Triple
T15265263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tannochside |
E364882
|
entity |
| Predicate | positionRelativeToGlasgow |
P71564
|
FINISHED |
| Object | eastern outskirts of Glasgow |
—
|
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: eastern outskirts of Glasgow | Statement: [Tannochside, positionRelativeToGlasgow, eastern outskirts of Glasgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToGlasgow Context triple: [Tannochside, positionRelativeToGlasgow, eastern outskirts of Glasgow]
-
A.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
-
B.
directionFromGlasgow
chosen
Indicates the compass direction in which one entity is located relative to Glasgow.
-
C.
geographicDirectionFromEdinburgh
Indicates the geographic direction in which one place or entity is located relative to Edinburgh.
-
D.
distanceToEdinburgh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
-
E.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.