Triple

T18475958
Position Surface form Disambiguated ID Type / Status
Subject Neil Snodgrass E451432 entity
Predicate name P16 FINISHED
Object Neil Snodgrass 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: Neil Snodgrass | Statement: [Neil Snodgrass, name, Neil Snodgrass]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neil Snodgrass
Context triple: [Neil Snodgrass, name, Neil Snodgrass]
  • A. Neil Snodgrass chosen
    Neil Snodgrass is an individual notable enough to be specifically cited as a bearer of the Snodgrass surname, though widely known public details about his life or achievements are limited.
  • B. Michael Snodgrass
    Michael Snodgrass is a person notable enough to be recognized as a bearer of the surname Snodgrass.
  • C. Paul Snodgrass
    Paul Snodgrass is a South African comedian, radio personality, and writer known for his stand-up performances and work in local media.
  • D. Patrick Snodgrass
    Patrick Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
  • E. Ian Snodgrass
    Ian Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass, though specific widely known achievements or roles are not clearly documented.
  • 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_69d8d38465a0819099b9b42d2a662ac1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53062f67881909620c4e8fc00eb7d completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 11:34 a.m.