Triple
T8000178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watlington |
E186227
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Watlington |
E186227
|
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: Watlington | Statement: [Watlington, hasPostTown, Watlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Watlington Context triple: [Watlington, hasPostTown, Watlington]
-
A.
Watlington
Watlington is a residential suburb located within the city of Timaru in the Canterbury region of New Zealand.
-
B.
Watlington
Watlington is a village in Norfolk, England, known for its rural character and location near the River Great Ouse.
-
C.
Watlington
chosen
Watlington is a small historic market town in Oxfordshire, England, known for its traditional high street and location near the Chiltern Hills.
-
D.
Wallington
Wallington is a suburban town in the London Borough of Sutton, known for its residential character, grammar schools, and green spaces in south London, England.
-
E.
Wallington
Wallington is a small rural village in the North Hertfordshire district of England, known for its historic buildings and traditional countryside character.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9b67988190a8a4a2c960017400 |
completed | March 31, 2026, 3:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe114372c819086f06e184d5ebde2 |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 5:17 p.m.