Triple
T11779367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Chichester Roman road |
E280101
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Ockley |
E280095
|
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: Ockley | Statement: [London–Chichester Roman road, passesThrough, Ockley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ockley Context triple: [London–Chichester Roman road, passesThrough, Ockley]
-
A.
Ockley
chosen
Ockley is a rural village in Surrey, England, known for its historic setting along the ancient Roman road of Stane Street.
-
B.
Wainhill
Wainhill is a small hamlet in Oxfordshire, England, situated near the village of Chinnor in the Chiltern Hills.
-
C.
Botesdale
Botesdale is a small rural village in Suffolk, England, known for its historic buildings and traditional village character.
-
D.
Besselsleigh
Besselsleigh is a small village and civil parish in Oxfordshire, England, known for its rural setting and historic manor.
-
E.
Oxley
Oxley is a surname of English origin borne by various notable individuals across politics, sports, and other fields.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5623f708190a18aea570577a3f6 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f090b8f4c481908cb3cf03875c0e24 |
completed | April 28, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:42 p.m.