Triple
T15130301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacorum |
E361400
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Potten End |
E769424
|
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: Potten End | Statement: [Dacorum, contains, Potten End]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Potten End Context triple: [Dacorum, contains, Potten End]
-
A.
Potten End
chosen
Potten End is a small rural village in Hertfordshire, England, known for its traditional village green and proximity to the town of Berkhamsted.
-
B.
Bennetts End
Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
-
C.
Colliers End
Colliers End is a small hamlet in the parish of Standon in Hertfordshire, England.
-
D.
Wollescote
Wollescote is a suburban area of Stourbridge in the West Midlands, England, known for its residential character and proximity to local parks and green spaces.
-
E.
Paddington End
Paddington End is one of the two named bowling ends at the Sydney Cricket Ground in Sydney, Australia.
- 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.