Triple
T4300485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snodgrass |
E99821
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Patrick Snodgrass
Patrick Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
|
E449438
|
NE FINISHED |
How this triple was built (4 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: Patrick Snodgrass | Statement: [Snodgrass, hasNotableBearer, Patrick Snodgrass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Patrick Snodgrass Context triple: [Snodgrass, hasNotableBearer, Patrick Snodgrass]
-
A.
Michael Snodgrass
Michael Snodgrass is a person notable enough to be recognized as a bearer of the surname Snodgrass.
-
B.
Richard Snodgrass
Richard Snodgrass is an American computer scientist known for his contributions to temporal databases and database systems research.
-
C.
John Snodgrass
John Snodgrass is a notable individual distinguished enough to be specifically recognized as a bearer of the Snodgrass surname.
-
D.
Charles Snodgrass
Charles Snodgrass is a person notable enough to be recognized as a primary bearer of the surname Snodgrass.
-
E.
Fred Snodgrass
Fred Snodgrass was an American Major League Baseball outfielder best remembered for his infamous dropped fly ball in the 1912 World Series.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Patrick Snodgrass Triple: [Snodgrass, hasNotableBearer, Patrick Snodgrass]
Generated description
Patrick Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Patrick Snodgrass Target entity description: Patrick Snodgrass is an individual notable enough to be recognized as a namesake of the surname Snodgrass.
-
A.
Michael Snodgrass
Michael Snodgrass is a person notable enough to be recognized as a bearer of the surname Snodgrass.
-
B.
Richard Snodgrass
Richard Snodgrass is an American computer scientist known for his contributions to temporal databases and database systems research.
-
C.
John Snodgrass
John Snodgrass is a notable individual distinguished enough to be specifically recognized as a bearer of the Snodgrass surname.
-
D.
Charles Snodgrass
Charles Snodgrass is a person notable enough to be recognized as a primary bearer of the surname Snodgrass.
-
E.
Fred Snodgrass
Fred Snodgrass was an American Major League Baseball outfielder best remembered for his infamous dropped fly ball in the 1912 World Series.
- F. None of above. chosen
Provenance (5 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509e8cb481909ccca7992aac31a3 |
completed | March 12, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bda4073aa88190ba64691b93aab900 |
completed | March 20, 2026, 7:46 p.m. |
| NEDg | Description generation | batch_69bda586202c8190960d36bdaa1284a7 |
completed | March 20, 2026, 7:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bda5dd44388190861ddf5f689b739c |
completed | March 20, 2026, 7:54 p.m. |
Created at: March 12, 2026, 11:08 p.m.