Triple
T10629258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Wales |
E250407
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Knighton |
E232423
|
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: Knighton | Statement: [Mid Wales, contains, Knighton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Knighton Context triple: [Mid Wales, contains, Knighton]
-
A.
Knighton
chosen
Knighton is a small market town on the English–Welsh border, known for its position on Offa’s Dyke and its surrounding rural landscapes.
-
B.
Knelston
Knelston is a small rural village located on the Gower Peninsula in South Wales, known for its scenic coastal surroundings and traditional Welsh character.
-
C.
Kintbury
Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
-
D.
Bedworth
Bedworth is a small market town in Warwickshire, England, situated between Coventry and Nuneaton and known historically for coal mining and ribbon weaving.
-
E.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df92f8388190a8bcff96809d8eb4 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96babc290819096c0c914d038ba01 |
completed | April 10, 2026, 9:29 p.m. |
Created at: April 8, 2026, 9 p.m.