Triple
T4792750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 635 (Texas) |
E106641
|
entity |
| Predicate | isPartOfLoop |
P48914
|
FINISHED |
| Object | Dallas beltway system |
—
|
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: Dallas beltway system | Statement: [Interstate 635 (Texas), isPartOfLoop, Dallas beltway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfLoop Context triple: [Interstate 635 (Texas), isPartOfLoop, Dallas beltway system]
-
A.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
B.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
-
C.
includedInCycle
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
D.
isOnLoopLine
chosen
Indicates that one entity (typically a route, track, or segment) lies on or belongs to a loop-shaped line or circuit within a network.
-
E.
hasBusLoop
Indicates that a location or facility includes a designated looped roadway or area specifically for bus circulation, stopping, or turning.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd66072ebc8190ae0e6cef1e7b07e4 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.