Triple
T3975555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yattendon |
E85631
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Yattendon |
E85631
|
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: Yattendon | Statement: [Yattendon, civilParish, Yattendon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yattendon Context triple: [Yattendon, civilParish, Yattendon]
-
A.
Yattendon
chosen
Yattendon is a small village and civil parish in Berkshire, England, known for its rural character and historic buildings.
-
B.
Coryton
Coryton is a suburban area and railway terminus in Cardiff, Wales, served by local commuter trains.
-
C.
Fenstanton
Fenstanton is a village and civil parish in Cambridgeshire, England, situated near the River Great Ouse between Huntingdon and St Ives.
-
D.
Bowdon
Bowdon is an affluent suburban area in Greater Manchester, England, known for its Victorian and Edwardian architecture and proximity to Altrincham.
-
E.
Chaldon
Chaldon is a small historic village in Surrey, England, noted for its ancient church and rural character within the Tandridge district.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef9b6d8008190822fceabe6542b3d |
completed | March 9, 2026, 4:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5401712188190aa6144dc1d5dcab6 |
completed | March 14, 2026, 11:01 a.m. |
Created at: March 9, 2026, 3:33 p.m.