Triple
T1394383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Pirates Hall of Fame |
E30631
|
entity |
| Predicate | firstInductionClassYear |
P24265
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Pittsburgh Pirates Hall of Fame, firstInductionClassYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstInductionClassYear Context triple: [Pittsburgh Pirates Hall of Fame, firstInductionClassYear, 2022]
-
A.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
B.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
C.
firstYearPlayed
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
D.
firstTestYear
Indicates the year in which an entity’s first test or testing activity took place.
-
E.
firstInductions
chosen
Indicates that the subject entity represents the earliest or initial instances in a series of inductions associated with the object 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37e60388190a8efcb345be7a1b9 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.