Triple
T18727010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quorn |
E457925
|
entity |
| Predicate | distanceToLoughborough |
P133334
|
FINISHED |
| Object | approximately 3 miles south |
—
|
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 3 miles south | Statement: [Quorn, distanceToLoughborough, approximately 3 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLoughborough Context triple: [Quorn, distanceToLoughborough, approximately 3 miles south]
-
A.
distanceToLeicester
Indicates the spatial distance between a given entity’s location and the location of Leicester.
-
B.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
C.
distanceToLuton_km
Indicates the distance, measured in kilometers, between a given entity’s location and Luton.
-
D.
distanceToLiverpoolCentral
Indicates the spatial distance between a given location and Liverpool Central.
-
E.
distanceToLichfield
Indicates the measured distance between a given location or entity and the place named Lichfield.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d74bd9881908cd314e68327c402 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.