Triple
T8266460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidetic script |
E193312
|
entity |
| Predicate | chronologicalStatus |
P81596
|
FINISHED |
| Object | extinct |
—
|
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: extinct | Statement: [Sidetic script, chronologicalStatus, extinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalStatus Context triple: [Sidetic script, chronologicalStatus, extinct]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
C.
chronologicallyClassifiedAs
Indicates that something is assigned to or placed within a specific time period or chronological category.
-
D.
hasChronologyStatus
Indicates the temporal or sequential status of something within a chronology, such as whether its position or order in time is known, uncertain, or otherwise classified.
-
E.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794e6880819084dff5df42332835 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:50 p.m.