Triple
T6289336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobham |
E140975
|
entity |
| Predicate | nearbyMotorwayJunction |
P16027
|
FINISHED |
| Object | M25 Junction 10 |
—
|
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: M25 Junction 10 | Statement: [Cobham, nearbyMotorwayJunction, M25 Junction 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMotorwayJunction Context triple: [Cobham, nearbyMotorwayJunction, M25 Junction 10]
-
A.
motorwayJunctionNearby
chosen
Indicates that a motorway junction is located close to the referenced entity.
-
B.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
C.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
D.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
E.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0641a6ecc8190a63be0e3f0344a3f |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:26 p.m.