Triple
T15720635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Norfolk |
E381082
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Shouldham |
E48861
|
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: Shouldham | Statement: [West Norfolk, containsSettlement, Shouldham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shouldham Context triple: [West Norfolk, containsSettlement, Shouldham]
-
A.
Shouldham
chosen
Shouldham is a small rural village in Norfolk, England, known for its traditional English countryside setting and historic character.
-
B.
Shalden
Shalden is a small rural village and civil parish in the East Hampshire district of Hampshire, England.
-
C.
Sebergham
Sebergham is a rural village and civil parish in Cumbria, England, known for its scenic countryside and historic character.
-
D.
Stadhampton
Stadhampton is a small rural village in Oxfordshire, England, known for its historic parish church and traditional English countryside setting.
-
E.
Hackham
Hackham is a southern suburb of Adelaide in South Australia, situated within the local government area of the City of Onkaparinga.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb0b51081908e652ec4992296fa |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff75852cf88190be054160d5cbc675 |
completed | May 9, 2026, 5:57 p.m. |
Created at: April 10, 2026, 4:45 a.m.