Triple
T33793831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insurgentes corridor |
E866009
|
entity |
| Predicate | roadTypeFollowed |
P1019
|
FINISHED |
| Object | urban arterial road |
—
|
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: urban arterial road | Statement: [Insurgentes corridor, roadTypeFollowed, urban arterial road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeFollowed Context triple: [Insurgentes corridor, roadTypeFollowed, urban arterial road]
-
A.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
C.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.