Triple
T4680948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvescot |
E103798
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Carterton |
E37630
|
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: Carterton | Statement: [Alvescot, hasNearbySettlement, Carterton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Carterton Context triple: [Alvescot, hasNearbySettlement, Carterton]
-
A.
Carterton
chosen
Carterton is a town in West Oxfordshire, England, known for its proximity to RAF Brize Norton and its role as a growing residential community.
-
B.
Poynton
Poynton is a town in Cheshire, England, known for its former coal mining industry and distinctive shared-space central junction.
-
C.
Coryton
Coryton is a suburban area and railway terminus in Cardiff, Wales, served by local commuter trains.
-
D.
Wilcote
Wilcote is a small rural village in the district of West Oxfordshire in Oxfordshire, England.
-
E.
Kedington
Kedington is a village and civil parish in the English county of Suffolk, known for its historic church and rural setting near Haverhill.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd636d306081908ff512896f54cb10 |
completed | March 20, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be03a8b7a88190bfc4f68438694995 |
completed | March 21, 2026, 2:34 a.m. |
Created at: March 20, 2026, 1:16 p.m.