Triple

T14505519
Position Surface form Disambiguated ID Type / Status
Subject Yelena Bonner E340254 entity
Predicate familyName P18 FINISHED
Object Bonner E637067 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: Bonner | Statement: [Yelena Bonner, familyName, Bonner]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bonner
Context triple: [Yelena Bonner, familyName, Bonner]
  • A. Bonner chosen
    Bonner is a residential suburb in the Gungahlin district of Canberra, Australian Capital Territory.
  • B. Bonderman
    Bonderman is a surname most prominently associated with American billionaire investor and private equity pioneer David Bonderman.
  • C. Boerne
    Boerne is a small, historic town in south-central Texas known for its German heritage, charming downtown, and scenic Hill Country surroundings.
  • D. Conerly
    Conerly is a surname most notably associated with Charlie Conerly, a prominent mid-20th-century American football quarterback.
  • E. Bivins
    Bivins is a surname most notably associated with Michael Bivins, an American singer, rapper, and music executive known for his work with New Edition and Bell Biv DeVoe.
  • 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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de94e25a2481908b8394e9a19f3b64 completed April 14, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6da07ff481909fb2463b0ea92849 completed May 8, 2026, 4:59 a.m.
Created at: April 10, 2026, 1:21 a.m.