Triple

T3529333
Position Surface form Disambiguated ID Type / Status
Subject Richard Olney E74619 entity
Predicate familyName P18 FINISHED
Object Olney E127998 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: Olney | Statement: [Richard Olney, familyName, Olney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Olney
Context triple: [Richard Olney, familyName, Olney]
  • A. Olney chosen
    Olney is a historic market town in southeast England, known for its traditional pancake race and association with the poet William Cowper.
  • B. Olney, Maryland
    Olney, Maryland is a suburban community in central Maryland known for its residential neighborhoods, good schools, and proximity to Washington, D.C.
  • C. Oakington
    Oakington is a village in Cambridgeshire, England, known for its rural character and proximity to the city of Cambridge.
  • D. Olneyville
    Olneyville is a historically industrial, working-class neighborhood in the west side of Providence, Rhode Island, known for its diverse population and ongoing urban revitalization.
  • E. Goodnestone
    Goodnestone is a small rural village and civil parish in Kent, England, known for its historic church and the nearby Goodnestone Park estate.
  • 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_69ad85d1a3948190931fd1ea1f49717b completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc6e9188819093480b39f263ce75 completed March 8, 2026, 6:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69b37e93c1988190a9ab7698bf63e8e6 completed March 13, 2026, 3:03 a.m.
Created at: March 8, 2026, 3:19 p.m.