Triple
T1165578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livingston |
E24590
|
entity |
| Predicate | distanceToGlasgow |
P18511
|
FINISHED |
| Object | approximately 30 miles east |
—
|
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: approximately 30 miles east | Statement: [Livingston, distanceToGlasgow, approximately 30 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGlasgow Context triple: [Livingston, distanceToGlasgow, approximately 30 miles east]
-
A.
distanceFromGlasgow
chosen
Indicates the spatial distance separating a given entity or location from Glasgow.
-
B.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
C.
distanceToDundee
Indicates the measured spatial distance between a given entity and the location of Dundee.
-
D.
distanceToKirkcaldy
Indicates the spatial distance between a given entity and the location of Kirkcaldy.
-
E.
distanceFromEdinburghWaverley
Indicates the measured distance between a given location and Edinburgh Waverley station.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.