Triple
T3762108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albuquerque Rapid Transit |
E82184
|
entity |
| Predicate | focusCorridorType |
P26881
|
FINISHED |
| Object | east–west urban corridor |
—
|
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: east–west urban corridor | Statement: [Albuquerque Rapid Transit, focusCorridorType, east–west urban corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusCorridorType Context triple: [Albuquerque Rapid Transit, focusCorridorType, east–west urban corridor]
-
A.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
B.
corridorType
chosen
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
C.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfa44ac819082f2c895d96c9170 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.