Triple
T26310024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muir of Ord |
E661795
|
entity |
| Predicate | distanceFromBeauly |
P195720
|
FINISHED |
| Object | approximately 3 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 3 miles east | Statement: [Muir of Ord, distanceFromBeauly, approximately 3 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBeauly Context triple: [Muir of Ord, distanceFromBeauly, approximately 3 miles east]
-
A.
distanceFromDalbeattie
Indicates the spatial distance between an entity and the location of Dalbeattie.
-
B.
distanceToAyr
Indicates the measured distance between a given entity or location and Ayr.
-
C.
distanceToBrechin
Indicates the spatial distance between a given entity or location and the place named Brechin.
-
D.
distanceToInverness
Indicates the spatial distance between a given entity and the location of Inverness.
-
E.
distanceToFraserburgh
Indicates the spatial distance between a given entity or location and Fraserburgh.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 26, 2026, 10:21 p.m.