Triple
T6090500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leek |
E135749
|
entity |
| Predicate | distanceToStokeOnTrent |
P68053
|
FINISHED |
| Object | approximately 10 miles northeast |
—
|
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 10 miles northeast | Statement: [Leek, distanceToStokeOnTrent, approximately 10 miles northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStokeOnTrent Context triple: [Leek, distanceToStokeOnTrent, approximately 10 miles northeast]
-
A.
distanceToCrewe
Indicates the spatial distance between an entity and the location Crewe.
-
B.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
C.
distanceToNottingham
Indicates the measured or estimated distance between a given location or entity and the city of Nottingham.
-
D.
distanceFromMiltonKeynes
Indicates the measured spatial distance between a given entity’s location and the location of Milton Keynes.
-
E.
distanceToStroud
Indicates the spatial distance between a given entity or location and the place named Stroud.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057aa192081908619d3518d4efa7a |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.