Triple
T8855484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haslingfield |
E210745
|
entity |
| Predicate | hasNearbyMajorRoad |
P49834
|
FINISHED |
| Object | M11 motorway (nearby) |
—
|
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: M11 motorway (nearby) | Statement: [Haslingfield, hasNearbyMajorRoad, M11 motorway (nearby)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMajorRoad Context triple: [Haslingfield, hasNearbyMajorRoad, M11 motorway (nearby)]
-
A.
nearbyMajorRoad
chosen
Indicates that one entity is located close to a significant or heavily used road.
-
B.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
E.
hasLocalRoad
Indicates that there exists a local road connection or association between the related entities.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c7f51881909c847989f31f203a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.