Triple
T28405693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culross village centre |
E719519
|
entity |
| Predicate | distanceToEdinburghApprox |
P21882
|
FINISHED |
| Object | about 20 miles northwest |
—
|
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 20 miles northwest | Statement: [Culross village centre, distanceToEdinburghApprox, about 20 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToEdinburghApprox Context triple: [Culross village centre, distanceToEdinburghApprox, about 20 miles northwest]
-
A.
distanceFromEdinburghApprox
chosen
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
B.
distanceToEdinburgh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
-
C.
distanceToGlasgowApprox
Indicates an approximate measure of how far something is from Glasgow.
-
D.
distanceFromEdinburghWaverley
Indicates the measured distance between a given location and Edinburgh Waverley station.
-
E.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: April 28, 2026, 1:23 a.m.