Triple
T23220096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen Expressway |
E580862
|
entity |
| Predicate | hasGradeSeparatedIntersections |
P31430
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Allen Expressway, hasGradeSeparatedIntersections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradeSeparatedIntersections Context triple: [Allen Expressway, hasGradeSeparatedIntersections, true]
-
A.
hasGradeSeparatedInterchanges
chosen
Indicates that the route or roadway includes interchanges where traffic flows are separated by different levels (e.g., overpasses/underpasses) rather than intersecting at the same grade.
-
B.
hasLaneSeparation
Indicates that there is a physical or marked separation between traffic lanes.
-
C.
isDividedHighway
Indicates that a roadway consists of physically separated carriageways for opposing directions of traffic.
-
D.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
E.
hasFreewaySegments
Indicates that one entity includes, contains, or is associated with specific freeway segments as part of its structure or network.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916870148190853874e6cf26bbc7 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.