Triple
T20411769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon |
E500602
|
entity |
| Predicate | containedTown |
P847
|
FINISHED |
| Object | Clevedon |
—
|
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: Clevedon | Statement: [Avon, containedTown, Clevedon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clevedon Context triple: [Avon, containedTown, Clevedon]
-
A.
Clevedon
chosen
Clevedon is a coastal town in southwest England known for its Victorian pier and views across the Severn Estuary.
-
B.
Clevedon
Clevedon is a rural locality and former parliamentary electorate in the Auckland Region of New Zealand.
-
C.
Penarth
Penarth is a seaside town in the Vale of Glamorgan, Wales, known for its Victorian pier, esplanade, and role as a filming location for various British television series.
-
D.
Highampton
Highampton is a small rural village and civil parish located in the West Devon district of Devon, England.
-
E.
Keynsham
Keynsham is a town in Somerset, England, situated between Bristol and Bath and known for its historic market-town character and riverside setting.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3f8fdc8190b05b6c41b38f34b7 |
completed | April 20, 2026, 7:10 p.m. |
Created at: April 16, 2026, 11:30 a.m.