Triple
T23854806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A404 road |
E592273
|
entity |
| Predicate | hasGradeSeparatedJunctions |
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: [A404 road, hasGradeSeparatedJunctions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradeSeparatedJunctions Context triple: [A404 road, hasGradeSeparatedJunctions, 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.
isDividedHighway
Indicates that a roadway consists of physically separated carriageways for opposing directions of traffic.
-
C.
hasRoadJunctionType
Indicates that a road junction has a specific type or classification (e.g., roundabout, intersection, interchange).
-
D.
hasLaneSeparation
Indicates that there is a physical or marked separation between traffic lanes.
-
E.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.