Triple
T16661194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakham |
E404862
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | OAKHAM |
E404862
|
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: OAKHAM | Statement: [Oakham, hasPostTown, OAKHAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OAKHAM Context triple: [Oakham, hasPostTown, OAKHAM]
-
A.
Oakham
chosen
Oakham is a historic market town in England’s East Midlands and the principal settlement of the county of Rutland.
-
B.
Hackham
Hackham is a southern suburb of Adelaide in South Australia, situated within the local government area of the City of Onkaparinga.
-
C.
Bookham
Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
-
D.
Bookham
Bookham is a small rural locality in New South Wales, Australia, situated along the Hume Highway and known for its agricultural surroundings and village community.
-
E.
Lyneham
Lyneham is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfee5448190bb44c4dadba5dcbd |
completed | April 18, 2026, 12:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084ce7cf0819091e7a4de2cc010ea |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.