Triple
T14344532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnton |
E355679
|
entity |
| Predicate | locatedInDirectionFromEdinburghCityCentre |
P29929
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Barnton, locatedInDirectionFromEdinburghCityCentre, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromEdinburghCityCentre Context triple: [Barnton, locatedInDirectionFromEdinburghCityCentre, northwest]
-
A.
geographicDirectionFromEdinburgh
chosen
Indicates the geographic direction in which one place or entity is located relative to Edinburgh.
-
B.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
C.
directionFromGlasgow
Indicates the compass direction in which one entity is located relative to Glasgow.
-
D.
distanceToEdinburgh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
-
E.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.