Triple
T21808371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emsian–Eifelian boundary |
E538406
|
entity |
| Predicate | chronologicRank |
P145731
|
FINISHED |
| Object | stage boundary within system |
—
|
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: stage boundary within system | Statement: [Emsian–Eifelian boundary, chronologicRank, stage boundary within system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicRank Context triple: [Emsian–Eifelian boundary, chronologicRank, stage boundary within system]
-
A.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologicalStatus
Indicates the temporal state or phase of something relative to a timeline or sequence of events.
-
E.
chronologicallyClassifiedAs
Indicates that something is assigned to or placed within a specific time period or chronological category.
- F. None of above. chosen
Provenance (4 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f078047ca88190a0efa4bc7f2faf80 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:53 p.m.