Triple
T35099203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverurie railway station |
E1012958
|
entity |
| Predicate | distanceFromAberdeenByRail |
P28185
|
FINISHED |
| Object | approximately 16 miles |
—
|
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 16 miles | Statement: [Inverurie railway station, distanceFromAberdeenByRail, approximately 16 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAberdeenByRail Context triple: [Inverurie railway station, distanceFromAberdeenByRail, approximately 16 miles]
-
A.
distanceToAberdeen
chosen
Indicates the spatial distance between a given entity and the location of Aberdeen.
-
B.
distanceToAyr
Indicates the measured distance between a given entity or location and Ayr.
-
C.
distanceToOban
Indicates the measured or calculated distance between a given entity or location and the place named Oban.
-
D.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
E.
directionFromAberdeen
Indicates the directional relationship of one place or object as measured outward starting from Aberdeen.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.