Triple
T4972327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newbridge |
E111681
|
entity |
| Predicate | roadJunctionStatus |
P41155
|
FINISHED |
| Object | key road junction |
—
|
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: key road junction | Statement: [Newbridge, roadJunctionStatus, key road junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadJunctionStatus Context triple: [Newbridge, roadJunctionStatus, key road junction]
-
A.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
B.
roadJunctionRelation
chosen
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
C.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
D.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.