Triple
T17757102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Snodgrass |
E443269
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Michael 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: Michael Snodgrass | Statement: [Michael Snodgrass, name, Michael Snodgrass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Michael Snodgrass Context triple: [Michael Snodgrass, name, Michael Snodgrass]
-
A.
Michael Snodgrass
chosen
Michael Snodgrass is a person notable enough to be recognized as a bearer of the surname Snodgrass.
-
B.
Neil Snodgrass
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.
-
C.
Brian Snodgrass
Brian Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
-
D.
Patrick Snodgrass
Patrick Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
-
E.
Paul Snodgrass
Paul Snodgrass is a South African comedian, radio personality, and writer known for his stand-up performances and work in local media.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841f29f08190b1a1e9624d88120f |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 10:10 a.m.