Triple
T6808261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Repton |
E156363
|
entity |
| Predicate | distanceToBurtonUponTrent |
P73122
|
FINISHED |
| Object | about 4 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: about 4 miles southeast | Statement: [Repton, distanceToBurtonUponTrent, about 4 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBurtonUponTrent Context triple: [Repton, distanceToBurtonUponTrent, about 4 miles southeast]
-
A.
distanceToStokeOnTrent
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
B.
distanceFromTamworth
Indicates the spatial distance measured from the reference location Tamworth to another place or entity.
-
C.
distanceToCrewe
Indicates the spatial distance between an entity and the location Crewe.
-
D.
distanceToNottingham
Indicates the measured or estimated distance between a given location or entity and the city of Nottingham.
-
E.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30b56c48190a5b244ea7e0c669a |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.