Triple
T20180694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EX postcode area |
E492717
|
entity |
| Predicate | coversTown |
P847
|
FINISHED |
| Object | Okehampton |
—
|
NE NERFINISHED |
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: Okehampton | Statement: [EX postcode area, coversTown, Okehampton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Okehampton Context triple: [EX postcode area, coversTown, Okehampton]
-
A.
Okehampton
chosen
Okehampton is a historic market town in Devon, England, known for its medieval castle and role as a former parliamentary borough.
-
B.
Cullompton
Cullompton is a historic market town in Devon, England, known for its agricultural heritage and location in the Culm Valley.
-
C.
Sompting
Sompting is a village and civil parish in West Sussex, England, situated near the south coast between Worthing and Lancing.
-
D.
Quidhampton
Quidhampton is a small village in Wiltshire, England, situated just west of Salisbury.
-
E.
Cinderford
Cinderford is a small industrial town in Gloucestershire, England, historically associated with coal mining and situated within the Forest of Dean.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668eed2e88190b54b15e6545dbdf8 |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.