Triple
T23087218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanefield |
E575640
|
entity |
| Predicate | distanceFromMilngavie |
P150876
|
FINISHED |
| Object | approximately 4 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: approximately 4 miles north | Statement: [Blanefield, distanceFromMilngavie, approximately 4 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMilngavie Context triple: [Blanefield, distanceFromMilngavie, approximately 4 miles north]
-
A.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
-
B.
distanceToGlasgowApprox
Indicates an approximate measure of how far something is from Glasgow.
-
C.
distanceFromEdinburghApprox
Indicates that an entity is located at an approximate distance from Edinburgh, rather than an exact measured distance.
-
D.
distanceToCoatbridge
Indicates the spatial distance between a given entity or location and the place named Coatbridge.
-
E.
distanceToEdinburgh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da652ac819085919ade6dd7bce4 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:57 p.m.