Triple

T18441546
Position Surface form Disambiguated ID Type / Status
Subject Ian Snodgrass E450539 entity
Predicate isAssociatedWith P2830 FINISHED
Object Snodgrass (surname) 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: Snodgrass (surname) | Statement: [Ian Snodgrass, isAssociatedWith, Snodgrass (surname)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Snodgrass (surname)
Context triple: [Ian Snodgrass, isAssociatedWith, Snodgrass (surname)]
  • A. Snodgrass chosen
    Snodgrass is a surname of English and Scottish origin borne by various notable individuals in sports, politics, and the arts.
  • B. Scott (surname)
    Scott is a common English and Scottish surname historically associated with people from Scotland or of Scottish descent.
  • C. Douglas (surname)
    Douglas (surname) is a Scottish family name of Gaelic origin historically associated with a powerful Lowland clan and widely borne in English-speaking countries.
  • D. Sturgis (surname)
    Sturgis is an English surname, historically derived from given names like Sturge and associated with families of Anglo-Norman and English origin.
  • E. Lynn (surname)
    Lynn is a surname of English and Scottish origin, often derived from place names meaning “lake” or “waterfall.”
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c10a86c819091196968b648fc92 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:30 a.m.