Triple
T22592995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charnwood |
E564997
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Wymeswold |
—
|
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: Wymeswold | Statement: [Charnwood, contains, Wymeswold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wymeswold Context triple: [Charnwood, contains, Wymeswold]
-
A.
Wymeswold
chosen
Wymeswold is a rural village and civil parish in the English East Midlands, known for its historic buildings and countryside setting within Leicestershire.
-
B.
Winkfield
Winkfield is a civil parish and village in Berkshire, England, situated within the unitary authority of Bracknell Forest.
-
C.
Wadesmill
Wadesmill is a small village in Hertfordshire, England, known historically as a coaching stop on the old Great North Road.
-
D.
Wroxton
Wroxton is a historic village in Oxfordshire, England, known for its traditional architecture, rural setting, and landmarks such as Wroxton Abbey and All Saints Church.
-
E.
Wroxton
Wroxton is a small rural community located in eastern Saskatchewan, Canada.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16163cb248190b377b110d80a6730 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 2:49 p.m.