Triple
T21356263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherwell district |
E526634
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ambrosden |
—
|
NE NERFINISHED |
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: Ambrosden | Statement: [Cherwell district, contains, Ambrosden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambrosden Context triple: [Cherwell district, contains, Ambrosden]
-
A.
Ambrosden
chosen
Ambrosden is a village and civil parish in Oxfordshire, England, located near the town of Bicester and known historically for its military connections.
-
B.
Balderstone
Balderstone is a district and residential area within the Balderstone and Kirkholt ward of Rochdale in Greater Manchester, England.
-
C.
Essendine
Essendine is a small village and civil parish in Rutland, England, known for its rural character and historic church.
-
D.
Aldhame
Aldhame is a historic coastal site in East Lothian, Scotland, notable for its early Christian associations and medieval chapel ruins.
-
E.
Roxeter
Roxeter is a historic settlement in Shropshire, England, known for its Roman origins and archaeological significance.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8afa0fca481908f1fd02154bcba9f |
completed | April 22, 2026, 11:23 a.m. |
Created at: April 16, 2026, 5:06 p.m.