Triple
T20394216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryton, United Kingdom |
E500157
|
entity |
| Predicate | distanceFromCoventry |
P74754
|
FINISHED |
| Object | approximately 5 miles southeast |
—
|
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 5 miles southeast | Statement: [Ryton, United Kingdom, distanceFromCoventry, approximately 5 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCoventry Context triple: [Ryton, United Kingdom, distanceFromCoventry, approximately 5 miles southeast]
-
A.
distanceToCoventry
chosen
Indicates the measured or specified distance between a given entity’s location and the city of Coventry.
-
B.
distanceToWolverhampton
Indicates the measured distance between a given location or entity and the place Wolverhampton.
-
C.
distanceToStokeOnTrent
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
D.
distanceToNuneaton
Indicates the spatial distance between a given location or entity and the town of Nuneaton.
-
E.
distanceToBirmingham
Indicates the spatial distance between a given entity’s location and the city of Birmingham.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679122058819083e3615a5ea0a82e |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.