Triple

T21846402
Position Surface form Disambiguated ID Type / Status
Subject Jon Tenney E539384 entity
Predicate hasSurname P18 FINISHED
Object Tenney NE NERFINISHED

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: Tenney | Statement: [Jon Tenney, hasSurname, Tenney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tenney
Context triple: [Jon Tenney, hasSurname, Tenney]
  • A. Tenney chosen
    Tenney is a surname most notably associated with American actor Jon Tenney, known for his work in film and television.
  • B. Will Tenneray
    Will Tenneray is a central gunslinger protagonist in the Western film "A Gunfight," known for his role in a high-stakes duel.
  • C. Ten’edn
    Ten’edn is an Aslian language spoken by an indigenous community in the Malay Peninsula, belonging to the broader Austroasiatic language family.
  • D. Edney
    Edney is a surname most notably associated with former UCLA and NBA basketball player Tyus Edney.
  • E. Tomlinson
    Tomlinson is a surname most notably associated with Ray Tomlinson, the American computer programmer credited with inventing networked email and introducing the "@" symbol in email addresses.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c476c3c88190a92d08ebb59a128a completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0bd546fb48190a7b815233650c2e7 completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:55 p.m.