Triple
T17667065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Snodgrass |
E440411
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | David 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: David Snodgrass | Statement: [David Snodgrass, name, David Snodgrass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: David Snodgrass Context triple: [David Snodgrass, name, David Snodgrass]
-
A.
David Snodgrass
chosen
David Snodgrass is a person notable enough to be specifically referenced as a bearer of the surname Snodgrass.
-
B.
Andrew Snodgrass
Andrew Snodgrass is an individual notable enough to be specifically cited as a bearer of the surname Snodgrass.
-
C.
Richard Snodgrass
Richard Snodgrass is an American computer scientist known for his contributions to temporal databases and database systems research.
-
D.
Steven Snodgrass
Steven Snodgrass is an individual notable enough to be specifically cited as a bearer of the Snodgrass surname.
-
E.
Charles Snodgrass
Charles Snodgrass is a person notable enough to be recognized as a primary bearer of the surname Snodgrass.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46eaaaec8819086977d8a5210c44e |
completed | April 19, 2026, 5:56 a.m. |
Created at: April 10, 2026, 9:58 a.m.