Triple

T16746181
Position Surface form Disambiguated ID Type / Status
Subject Empingham E406960 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: [Empingham, hasPostTown, Oakham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oakham
Context triple: [Empingham, 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. Bearbrook
    Bearbrook is a small river or stream running through the town of Aylesbury in Buckinghamshire, England.
  • C. Hamstead
    Hamstead is a suburban residential area in the West Midlands, England, situated between Birmingham and Sandwell.
  • D. Loughborough
    Loughborough is a large market and university town in Leicestershire, England, known for Loughborough University and its strong engineering and sports science reputation.
  • E. Leamington
    Leamington is a town in southwestern Ontario, Canada, known for its greenhouse agriculture and proximity to Point Pelee National Park on the shores of Lake Erie.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3aa223aa88190a3c1805ece7317e2 completed April 18, 2026, 3:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c798389c8190aa9865d9aa746da5 completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:21 a.m.