Triple
T3625178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herefordshire |
E76820
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kington |
E42591
|
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: Kington | Statement: [Herefordshire, contains, Kington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kington Context triple: [Herefordshire, contains, Kington]
-
A.
Kington
chosen
Kington is a small historic market town in Herefordshire, England, near the Welsh border, known for its scenic countryside and walking trails.
-
B.
Ketteringham
Ketteringham is a small village and civil parish in Norfolk, England, known for its rural character and historic parish church.
-
C.
Kingham
Kingham is a picturesque rural village in the Cotswolds area of Oxfordshire, England, known for its traditional stone cottages and countryside setting.
-
D.
Cretingham
Cretingham is a small rural village and civil parish in the English county of Suffolk, known for its historic church and countryside setting.
-
E.
Kessingland
Kessingland is a coastal village and civil parish in Suffolk, England, known for its long shingle beach and seaside tourism.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dae7a48190809d4455b2349aaa |
completed | March 8, 2026, 6:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4332260cc8190964a15bfee0a3b61 |
completed | March 13, 2026, 3:54 p.m. |
Created at: March 8, 2026, 3:23 p.m.