Triple
T481614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Yastrzemski |
E9179
|
entity |
| Predicate | battingTitle |
P7543
|
FINISHED |
| Object | American League batting champion |
—
|
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: American League batting champion | Statement: [Carl Yastrzemski, battingTitle, American League batting champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingTitle Context triple: [Carl Yastrzemski, battingTitle, American League batting champion]
-
A.
battedTitleLeague
Indicates that an entity held a batting title in a specified league.
-
B.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
C.
superBowlTitle
Indicates that one entity is the winner (holder) of a specified Super Bowl championship title.
-
D.
ledLeagueInBattingAverage
chosen
Indicates that an entity achieved the highest batting average in a particular league over a specified season or time period.
-
E.
BabeRuthRole
Indicates that an entity holds the specific role or position associated with Babe Ruth (e.g., as a legendary baseball player or cultural figure) in relation to another entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f05a7f6c819082b4a5a3e69468a6 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.