Triple
T17077386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunstable, Bedfordshire, England |
E414385
|
entity |
| Predicate | distanceToLuton |
P96407
|
FINISHED |
| Object | about 5 miles |
—
|
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 5 miles | Statement: [Dunstable, Bedfordshire, England, distanceToLuton, about 5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLuton Context triple: [Dunstable, Bedfordshire, England, distanceToLuton, about 5 miles]
-
A.
distanceToLuton_km
Indicates the distance, measured in kilometers, between a given entity’s location and Luton.
-
B.
distanceToCentralLuton
chosen
Indicates the measured or calculated distance between an entity’s location and the central area of Luton.
-
C.
distanceToHertford
Indicates the spatial distance between a given entity and the location of Hertford.
-
D.
distanceToTelford
Indicates the spatial distance between a given entity and the location of Telford.
-
E.
distanceToNuneaton
Indicates the spatial distance between a given location or entity and the town of Nuneaton.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc625c48190b679a521180e10ad |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.