Triple
T5180775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congleton |
E116913
|
entity |
| Predicate | distanceToCrewe |
P62214
|
FINISHED |
| Object | approximately 11 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 11 miles north | Statement: [Congleton, distanceToCrewe, approximately 11 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCrewe Context triple: [Congleton, distanceToCrewe, approximately 11 miles north]
-
A.
distanceToWolverhampton
Indicates the measured distance between a given location or entity and the place Wolverhampton.
-
B.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
C.
distanceToRochdale
Indicates the spatial distance between a given entity’s location and the location of Rochdale.
-
D.
distanceFromTamworth
Indicates the spatial distance measured from the reference location Tamworth to another place or entity.
-
E.
distanceToSalford
Indicates the spatial distance between a given entity and the location of Salford.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799a322c8190b8a590cfe70761f5 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79251b548190918a1eb930e24c22 |
completed | March 20, 2026, 4:43 p.m. |
Created at: March 20, 2026, 1:45 p.m.