Triple
T8372897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinton, Wiltshire |
E197501
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Wilton |
E218409
|
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: Wilton | Statement: [Dinton, Wiltshire, near, Wilton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilton Context triple: [Dinton, Wiltshire, near, Wilton]
-
A.
Wilton
chosen
Wilton was a former UK parliamentary constituency in Wiltshire, historically represented in the House of Commons before its abolition in the 19th century.
-
B.
Wilton
Wilton is a town in Saratoga County, New York, known for its suburban communities, commercial development, and proximity to Saratoga Springs.
-
C.
Wilton
Wilton is a small New Hampshire town known for its rural character, historic mill village, and location along the Souhegan River.
-
D.
Wilton
Wilton is a small village in North Yorkshire, England, situated within the unitary authority area of Redcar and Cleveland.
-
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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a6944081909c4547688c9e70ae |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce02aab4488190abc63bace296e32a |
completed | April 2, 2026, 5:46 a.m. |
Created at: March 30, 2026, 6:01 p.m.