Triple
T17077385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunstable, Bedfordshire, England |
E414385
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Luton |
E51115
|
NE 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: Luton | Statement: [Dunstable, Bedfordshire, England, near, Luton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luton Context triple: [Dunstable, Bedfordshire, England, near, Luton]
-
A.
Luton
chosen
Luton is a large town in Bedfordshire, England, known for its international airport and diverse urban population.
-
B.
Aylesbury
Aylesbury is a historic market town in southern England that serves as an important commercial and administrative center in Buckinghamshire.
-
C.
Hemel Hempstead
Hemel Hempstead is a large town in southern England, known as a post-war New Town and major commercial and residential centre within Hertfordshire.
-
D.
Hertford
Hertford is a small historic town in northeastern North Carolina known for its riverside setting and traditional Southern charm.
-
E.
Hertford
Hertford is a historic market town and the county town of Hertfordshire in southern England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139f7e6408190978c940c6e641d47 |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:34 a.m.