Triple
T30753884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas beltway system |
E783026
|
entity |
| Predicate | outerLoopComponent |
P103593
|
FINISHED |
| Object | Interstate 20 |
—
|
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 20 | Statement: [Dallas beltway system, outerLoopComponent, Interstate 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerLoopComponent Context triple: [Dallas beltway system, outerLoopComponent, Interstate 20]
-
A.
partOfLoopWith
chosen
Indicates that one entity participates as a component or segment within the same loop structure as another entity.
-
B.
isLoopOf
Indicates that one entity represents a loop or cyclic structure corresponding to, derived from, or associated with another entity.
-
C.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
D.
directionRelativeToOuterLoop
Indicates the orientation or turning direction of an element relative to the path or traversal direction of an enclosing outer loop.
-
E.
upperComponent
Indicates that one component is positioned above or on top of another component within a larger structure or assembly.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f93f8b48190aebe0bbbd662f07b |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.