Triple
T25851456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1904 World Series |
E651220
|
entity |
| Predicate | giantsRefusalDecisionMaker |
P76461
|
FINISHED |
| Object | John T. Brush |
—
|
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: John T. Brush | Statement: [1904 World Series, giantsRefusalDecisionMaker, John T. Brush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: giantsRefusalDecisionMaker Context triple: [1904 World Series, giantsRefusalDecisionMaker, John T. Brush]
-
A.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
B.
giantsStatus
Indicates the current condition, role, or standing of the Giants within a given context (such as a game, season, or league).
-
C.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
D.
wasDecidedBy
chosen
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
E.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
- F. None of above.
Provenance (3 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023b96208190925872085ada10e3 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:58 a.m.