Triple
T18005033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winchester District |
E430723
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Durley |
E751121
|
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: Durley | Statement: [Winchester District, contains, Durley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durley Context triple: [Winchester District, contains, Durley]
-
A.
Durley
chosen
Durley is a small rural village in Hampshire, England, known for its countryside setting and traditional English character.
-
B.
Reydon
Reydon is a village and civil parish in the English county of Suffolk, located near the coastal town of Southwold.
-
C.
Dahlbury
Dahlbury is a company known for its commercial sponsorship of sporting events such as the Coronation Cup.
-
D.
Umberleigh
Umberleigh is a small rural village in North Devon, England, situated on the River Taw and served by a local railway station.
-
E.
Durford
Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51ba1888190a339d726e92f376b |
completed | April 19, 2026, 10:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0337b6b7e48190a649dda888450b2d |
completed | May 12, 2026, 2:22 p.m. |
Created at: April 10, 2026, 10:23 a.m.