Triple

T5314836
Position Surface form Disambiguated ID Type / Status
Subject Chaka Khan E119120 entity
Predicate hasFamilyName P18 FINISHED
Object Stevens E26256 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: Stevens | Statement: [Chaka Khan, hasFamilyName, Stevens]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stevens
Context triple: [Chaka Khan, hasFamilyName, Stevens]
  • A. Stevens chosen
    Stevens is a common English-language surname borne by numerous notable individuals across fields such as sports, politics, arts, and academia.
  • B. Hillegas
    Hillegas is a surname most notably associated with Michael Hillegas, the first Treasurer of the United States.
  • C. Rutledge
    Rutledge is a small town in eastern Tennessee that serves as the county seat of Grainger County within the Knoxville metropolitan area.
  • D. Rutledge
    Rutledge is a surname of English and Scottish origin borne by various notable individuals in politics, law, and other fields.
  • E. Shaughnessy
    Shaughnessy is an affluent residential neighbourhood in Vancouver, British Columbia, known for its large heritage homes and tree-lined streets.
  • 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_69bd446b57bc8190a513d2e6c40314f3 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd854d947081909e51b27e40940580 completed March 20, 2026, 5:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf110ad9688190aa74122adb8ee52d completed March 21, 2026, 9:43 p.m.
Created at: March 20, 2026, 1:54 p.m.