Triple
T222112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deacon Phillippe |
E4235
|
entity |
| Predicate | inductionYear |
P7533
|
FINISHED |
| Object | 2023 (Pittsburgh Pirates Hall of Fame) |
—
|
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: 2023 (Pittsburgh Pirates Hall of Fame) | Statement: [Deacon Phillippe, inductionYear, 2023 (Pittsburgh Pirates Hall of Fame)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inductionYear Context triple: [Deacon Phillippe, inductionYear, 2023 (Pittsburgh Pirates Hall of Fame)]
-
A.
hallOfFameInductionYear
chosen
Indicates the year in which an entity was formally inducted into a hall of fame.
-
B.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
C.
inductedInto
Indicates that an entity has been formally admitted or entered into a group, organization, hall of fame, or similar body, typically as an honor or official recognition.
-
D.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
-
E.
teamHallOfFameInduction
Indicates that an individual has been formally inducted into a specific team’s Hall of Fame.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.