Triple
T28485767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Stratton |
E720823
|
entity |
| Predicate | hasRoadBypassPlanned |
P113407
|
FINISHED |
| Object | Long Stratton bypass |
—
|
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: Long Stratton bypass | Statement: [Long Stratton, hasRoadBypassPlanned, Long Stratton bypass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadBypassPlanned Context triple: [Long Stratton, hasRoadBypassPlanned, Long Stratton bypass]
-
A.
isTollRoadPlanned
Indicates that a road is intended or scheduled to become a toll road in the future.
-
B.
roadBypassedInYear
Indicates that a particular road was bypassed or replaced by an alternative route in the specified year.
-
C.
hasNumberOfSlipRoads
Indicates the number of slip roads (on/off ramps) associated with a particular road segment or junction.
-
D.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
-
E.
bypassesCity
chosen
Indicates that a route, road, or path goes around a city rather than passing directly through it.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 2:58 a.m.