Triple
T6419159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tain |
E127900
|
entity |
| Predicate | distanceToInverness |
P70555
|
FINISHED |
| Object | about 35 miles north |
—
|
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: about 35 miles north | Statement: [Tain, distanceToInverness, about 35 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToInverness Context triple: [Tain, distanceToInverness, about 35 miles north]
-
A.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
B.
distanceToBrechin
Indicates the spatial distance between a given entity or location and the place named Brechin.
-
C.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
-
D.
distanceToDundee
Indicates the measured spatial distance between a given entity and the location of Dundee.
-
E.
distanceToAberdeen
Indicates the spatial distance between a given entity and the location of Aberdeen.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690194dc8190b3382bd5f92876b5 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:43 p.m.