Triple
T4068040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Tew |
E86375
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Enstone |
E95346
|
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: Enstone | Statement: [Little Tew, nearbySettlement, Enstone]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enstone Context triple: [Little Tew, nearbySettlement, Enstone]
-
A.
Enstone
chosen
Enstone is a rural village in Oxfordshire, England, known for its historic buildings and picturesque Cotswold countryside setting.
-
B.
Aston
Aston is a masculine given name of English origin, used both as a first name and a surname.
-
C.
Aston
Aston is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
-
D.
Chandlers Ford
Chandlers Ford is a suburban town in Hampshire, England, situated between Southampton and Winchester and known primarily as a residential and commuter area.
-
E.
Goodwood
Goodwood is the codename for Operation Goodwood, a major British armoured offensive conducted during the Battle of Normandy in World War II.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf8f33c8190a6afca1830f35485 |
completed | March 9, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562b48fc481908547d51aae15e959 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.