Triple
T16839295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babraham Road |
E409364
|
entity |
| Predicate | directionFromCambridgeCityCentre |
P84631
|
FINISHED |
| Object | 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: southeast | Statement: [Babraham Road, directionFromCambridgeCityCentre, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromCambridgeCityCentre Context triple: [Babraham Road, directionFromCambridgeCityCentre, southeast]
-
A.
directionFromCambridge
chosen
Indicates the compass direction or bearing of one place or object as measured outward starting from Cambridge.
-
B.
distanceFromCambridgeCentre
Indicates the spatial distance between a given entity and the central point of Cambridge.
-
C.
directionFromOxford
Indicates the cardinal or relative compass direction of one place or object as measured from Oxford.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
E.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
- 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.