Triple
T15942456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SY postcode area |
E386598
|
entity |
| Predicate | hasPostTown |
P2711
|
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: [SY postcode area, hasPostTown, Knighton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Knighton Context triple: [SY postcode area, hasPostTown, 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.
Quidhampton
Quidhampton is a small village in Wiltshire, England, situated just west of Salisbury.
-
D.
Cuxton
Cuxton is a village and civil parish in the Medway unitary authority of Kent, England, situated on the River Medway.
-
E.
Kintbury
Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156ce0230819089a20114a755a75a |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5bbc07c819098fd768e2e6b5b3e |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.