Triple
T29179562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deşli Caira section |
E739708
|
entity |
| Predicate | boundaryLevel |
P153814
|
FINISHED |
| Object | base of the Anisian Stage |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: base of the Anisian Stage | Statement: [Deşli Caira section, boundaryLevel, base of the Anisian Stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryLevel Context triple: [Deşli Caira section, boundaryLevel, base of the Anisian Stage]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
boundaryStatus
Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
-
C.
boundaryMetric
Indicates a relationship where a quantitative measure is assigned to the boundary or interface between entities, capturing some property (such as distance, similarity, or cost) of that boundary.
-
D.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
E.
boundarySignature
chosen
Indicates the defining boundary or outer limit that characterizes or uniquely identifies a region, object, or domain.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663444268819088b7976a7295d57a |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:56 a.m.