Triple
T35859615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 World Series |
E1036908
|
entity |
| Predicate | notablePitcherForYankees |
P7082
|
FINISHED |
| Object | Red Ruffing |
E809079
|
NE FINISHED |
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: Red Ruffing | Statement: [1938 World Series, notablePitcherForYankees, Red Ruffing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePitcherForYankees Context triple: [1938 World Series, notablePitcherForYankees, Red Ruffing]
-
A.
notablePitcher
chosen
Indicates that the subject is recognized as a distinguished or prominent pitcher in the context of baseball.
-
B.
notablePitcherPerformance
Indicates a relationship where a pitcher delivers an especially outstanding or remarkable performance in a game or season.
-
C.
YankeesStarPlayer
Indicates that the subject is a standout or key player for the New York Yankees baseball team.
-
D.
CyYoungEra
Indicates that a pitcher’s earned run average (ERA) in a given season was at a level typically associated with Cy Young Award–caliber performance.
-
E.
playedForYankeesUntil
Indicates that an entity was a member of and played for the New York Yankees up to and including a specified end time.
- F. None of above.
Provenance (4 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4e6b3f0819094f57043c295ac91 |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.