Triple

T22232356
Position Surface form Disambiguated ID Type / Status
Subject Michael Radford E549497 entity
Predicate familyName P18 FINISHED
Object Radford 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: Radford | Statement: [Michael Radford, familyName, Radford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radford
Context triple: [Michael Radford, familyName, Radford]
  • A. Radford chosen
    Radford is a masculine given name of English origin that has been used both as a first name and surname.
  • B. Radford, Virginia
    Radford, Virginia is an independent city in southwestern Virginia known for being home to Radford University and its location along the New River.
  • C. Lawford
    Lawford is a village in Essex, England, situated within the scenic Dedham Vale Area of Outstanding Natural Beauty.
  • D. Lawford
    Lawford is an English-origin surname most notably associated with actor Peter Lawford and, by marriage, the Kennedy political family.
  • E. Montclar
    Montclar is a small municipality in the Berguedà comarca of Catalonia, Spain, known for its rural landscape and traditional Catalan character.
  • 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_69e11e4102b881909cf47d3768e25c19 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12bf3de648190986a734f19643a8c completed April 28, 2026, 9:51 p.m.
Created at: April 16, 2026, 8:38 p.m.