Triple
T15130298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacorum |
E361400
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bovingdon |
E233094
|
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: Bovingdon | Statement: [Dacorum, contains, Bovingdon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bovingdon Context triple: [Dacorum, contains, Bovingdon]
-
A.
Bovingdon
chosen
Bovingdon is a large village and civil parish in Hertfordshire, England, known for its historic airfield and proximity to the town of Hemel Hempstead.
-
B.
Harpenden
Harpenden is a commuter town in southern England known for its green spaces and affluent residential character.
-
C.
Brinsdon
Brinsdon is a small settlement located within the civil parish of Yeovilton in Somerset, England.
-
D.
Waldringfield
Waldringfield is a small riverside village in eastern England known for its scenic setting on the River Deben and sailing activities.
-
E.
Wormley
Wormley is a village and civil parish in Hertfordshire, England, known for its residential character and proximity to the Lea Valley.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7fa449c8190aed8941168b063c3 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:06 a.m.