Triple
T16839304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babraham Road |
E409364
|
entity |
| Predicate | isApproachRouteTo |
P6174
|
FINISHED |
| Object | Cambridge city from southeast |
—
|
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: Cambridge city from southeast | Statement: [Babraham Road, isApproachRouteTo, Cambridge city from southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isApproachRouteTo Context triple: [Babraham Road, isApproachRouteTo, Cambridge city from southeast]
-
A.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
B.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
C.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
-
D.
isAccessRouteAround
Indicates that one entity serves as an access route that goes around or circumvents another entity.
-
E.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34f902c8190a334ba7caa04ce7e |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.