Triple
T8386660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Evans |
E197832
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Youlbury |
E734384
|
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: Youlbury | Statement: [Arthur Evans, residence, Youlbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Youlbury Context triple: [Arthur Evans, residence, Youlbury]
-
A.
Youlbury
chosen
Youlbury is a rural locality in Oxfordshire, England, known historically as the place where archaeologist Sir Arthur Evans died.
-
B.
Oldbury
Oldbury is a town in the West Midlands of England that serves as the administrative centre of the Metropolitan Borough of Sandwell.
-
C.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
D.
Wraysbury
Wraysbury is a village and civil parish in Berkshire, England, situated near the River Thames and known for its historic sites and proximity to Windsor.
-
E.
Dahlbury
Dahlbury is a company known for its commercial sponsorship of sporting events such as the Coronation Cup.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3967fd108190b045ea1328b1dc4b |
completed | April 2, 2026, 9:39 a.m. |
Created at: March 30, 2026, 6:03 p.m.