Triple
T29179563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deşli Caira section |
E739708
|
entity |
| Predicate | stageBoundary |
P64686
|
FINISHED |
| Object | Olenekian–Anisian boundary |
—
|
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: Olenekian–Anisian boundary | Statement: [Deşli Caira section, stageBoundary, Olenekian–Anisian boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageBoundary Context triple: [Deşli Caira section, stageBoundary, Olenekian–Anisian boundary]
-
A.
startBoundary
chosen
Indicates the point, limit, or marker where something begins or where a specified interval, region, or process first comes into effect.
-
B.
stageLimitDefinition
Indicates a defined constraint or maximum allowable value associated with a particular stage in a process or sequence.
-
C.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
-
D.
stageCriterion
Indicates that a specific condition or requirement is used to determine or classify the stage or phase of a process, object, or entity.
-
E.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
- 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_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 11:56 a.m.