Triple

T23281470
Position Surface form Disambiguated ID Type / Status
Subject John T. Connor E588873 entity
Predicate familyName P18 FINISHED
Object Connor 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: Connor | Statement: [John T. Connor, familyName, Connor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Connor
Context triple: [John T. Connor, familyName, Connor]
  • A. Connor chosen
    Connor is a surname most infamously associated with Bull Connor, the segregationist Birmingham, Alabama public safety commissioner whose brutal tactics against civil rights protesters in the 1960s drew national outrage.
  • B. Connor
    Connor is a major character from the TV series "Angel," known as the superhuman son of the vampire Angel and central to several of the show's key storylines.
  • C. Connor
    Connor is a historic town in County Antrim, Northern Ireland, traditionally associated with an early Christian bishopric.
  • D. Connor
    Connor is a masculine given name of Irish origin, commonly used in English-speaking countries.
  • E. Conor
    Conor is a masculine given name of Irish origin, commonly used in English-speaking countries.
  • 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19643b8908190a2c29552b272dc61 completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:57 p.m.