Triple
T28841181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 493 |
E728317
|
entity |
| Predicate | precededByInNumbering |
P39998
|
FINISHED |
| Object | Interstate 492 (hypothetical in sequence) |
—
|
NE NERFINISHED |
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: Interstate 492 (hypothetical in sequence) | Statement: [Interstate 493, precededByInNumbering, Interstate 492 (hypothetical in sequence)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByInNumbering Context triple: [Interstate 493, precededByInNumbering, Interstate 492 (hypothetical in sequence)]
-
A.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
B.
precededByInGroup
Indicates that one entity comes before another in the ordered sequence within the same group or collection.
-
C.
precedesNumeral
chosen
Indicates that one numeral comes before another numeral in a specified ordering or sequence.
-
D.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
-
E.
classPrecededBy
Indicates that one class occurs or is scheduled before another class in a sequence or timetable.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 6:40 a.m.