Triple
T7635276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threemiletown |
E172861
|
entity |
| Predicate | distanceToLinlithgow |
P77460
|
FINISHED |
| Object | approximately 3 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 3 miles | Statement: [Threemiletown, distanceToLinlithgow, approximately 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLinlithgow Context triple: [Threemiletown, distanceToLinlithgow, approximately 3 miles]
-
A.
distanceFromGlasgow
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.
distanceToKirkcaldy
Indicates the spatial distance between a given entity and the location of Kirkcaldy.
-
D.
distanceFromEdinburghWaverley
Indicates the measured distance between a given location and Edinburgh Waverley station.
-
E.
distanceToInverness
Indicates the spatial distance between a given entity and the location of Inverness.
- F. None of above. chosen
Provenance (4 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa83fcc8190a3f0bb20cbe1b2d6 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:57 p.m.