Triple
T4431758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enstone |
E95346
|
entity |
| Predicate | hasSettlementPart |
P8239
|
FINISHED |
| Object | Neat 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: Neat Enstone | Statement: [Enstone, hasSettlementPart, Neat Enstone]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neat Enstone Context triple: [Enstone, hasSettlementPart, Neat Enstone]
-
A.
Rudge
Rudge is a character from Alan Bennett’s play and film "The History Boys," known as one of the students whose academic potential is initially underestimated.
-
B.
Aston
Aston is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
-
C.
Aston
Aston is a masculine given name of English origin, used both as a first name and a surname.
-
D.
Enstone
chosen
Enstone is a rural village in Oxfordshire, England, known for its historic buildings and picturesque Cotswold countryside setting.
-
E.
Hulton Park
Hulton Park was a historic landed estate in Lancashire, England, long associated with the Hulton family and their coal-mining interests.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556b71448190a3fab938853f8b87 |
completed | March 13, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b6136f350c81908d00eff850951ab0 |
completed | March 15, 2026, 2:03 a.m. |
Created at: March 12, 2026, 11:31 p.m.