Triple
T5631609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pridoli Epoch |
E147845
|
entity |
| Predicate | positionInPeriod |
P10549
|
FINISHED |
| Object | final epoch of the Silurian Period |
—
|
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: final epoch of the Silurian Period | Statement: [Pridoli Epoch, positionInPeriod, final epoch of the Silurian Period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPeriod Context triple: [Pridoli Epoch, positionInPeriod, final epoch of the Silurian Period]
-
A.
positionInSeason
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
-
B.
positionInEra
chosen
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
C.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225cdcdc819095034f12c39ef755 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.