Triple
T19471540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Giants 1900–1916 |
E487133
|
entity |
| Predicate | notablePlayer |
P304
|
FINISHED |
| Object | Fred 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: Fred Snodgrass | Statement: [New York Giants 1900–1916, notablePlayer, Fred Snodgrass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fred Snodgrass Context triple: [New York Giants 1900–1916, notablePlayer, Fred Snodgrass]
-
A.
Fred Snodgrass
chosen
Fred Snodgrass was an American Major League Baseball outfielder best remembered for his infamous dropped fly ball in the 1912 World Series.
-
B.
Charles Snodgrass
Charles Snodgrass is a person notable enough to be recognized as a primary 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.
David Snodgrass
David Snodgrass is a person notable enough to be specifically referenced as a bearer of the surname Snodgrass.
-
E.
Steven Snodgrass
Steven Snodgrass is an individual notable enough to be specifically cited as a bearer of the Snodgrass surname.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e8d9188190a4939f03bad89add |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 10, 2026, 1:39 p.m.