Triple
T1171727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grover Cleveland Alexander |
E24925
|
entity |
| Predicate | ledLeagueInERA |
P24593
|
FINISHED |
| Object | 1915 |
—
|
LITERAL 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: 1915 | Statement: [Grover Cleveland Alexander, ledLeagueInERA, 1915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledLeagueInERA Context triple: [Grover Cleveland Alexander, ledLeagueInERA, 1915]
-
A.
careerEarnedRunAverage
Indicates the average number of earned runs a pitcher allows per nine innings over the entire span of their career.
-
B.
ledLeagueInBattingAverage
Indicates that an entity achieved the highest batting average in a particular league over a specified season or time period.
-
C.
careerERA
Indicates the earned run average (ERA) a pitcher maintains over the entirety of their professional career.
-
D.
ledLeagueInRBIs
Indicates that the subject had the highest number of runs batted in (RBIs) in a particular league over a specified season or time period.
-
E.
ledLeagueInHomeRuns
Indicates that the subject achieved the highest number of home runs in a particular league over a specified season or time period.
- F. None of above. chosen
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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bceb3f188190b8b767380fe5986f |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbd7ff1881908c943ecdfea59e81 |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:45 p.m.