Triple
T37499872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 255 |
E931926
|
entity |
| Predicate | hasAuxiliaryNumberOf |
P195378
|
FINISHED |
| Object | Interstate 55 |
—
|
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 55 | Statement: [Interstate 255, hasAuxiliaryNumberOf, Interstate 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuxiliaryNumberOf Context triple: [Interstate 255, hasAuxiliaryNumberOf, Interstate 55]
-
A.
hasAuxiliaryType
Indicates that an entity is associated with a secondary or supporting type that complements its primary classification.
-
B.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
C.
hasAuxiliaryEquipment
Indicates that one entity is equipped with, or accompanied by, additional supporting equipment associated with another entity.
-
D.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
E.
hasSecondaryComponent
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.