Triple
T102165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Yastrzemski |
E2061
|
entity |
| Predicate | hallOfFameInductionYear |
P7533
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Carl Yastrzemski, hallOfFameInductionYear, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hallOfFameInductionYear Context triple: [Carl Yastrzemski, hallOfFameInductionYear, 1989]
-
A.
hallOfFamePlayer
Indicates that the subject is recognized as a member of a designated Hall of Fame.
-
B.
allStarGameName
Indicates the specific name or title assigned to an All-Star Game event associated with an entity.
-
C.
allStarGame
Indicates that an entity participated in, was selected for, or is otherwise associated with an All-Star Game event.
-
D.
retiredNumberHonoree
Indicates that an entity is honored by having its jersey or identification number formally retired by a team or organization.
-
E.
hallOfFameStatus
Indicates whether an entity has been recognized with hall of fame status, typically signifying exceptional achievement or distinction within a particular field.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2563a6ff48190bec582fb2f99b7af |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258de46888190835db2b21a093eaa |
completed | Feb. 28, 2026, 2:54 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.