Triple
T13781462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Slam |
E331139
|
entity |
| Predicate | calendarYearRequirement |
P7173
|
FINISHED |
| Object | January to December |
—
|
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: January to December | Statement: [Golden Slam, calendarYearRequirement, January to December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarYearRequirement Context triple: [Golden Slam, calendarYearRequirement, January to December]
-
A.
confirmationYear
Indicates the calendar year in which a confirmation event or formal validation of something took place.
-
B.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
C.
yearPassed
Indicates that a specified number of calendar years has elapsed between two time points or events.
-
D.
yearType
chosen
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
E.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe98b5bc8190967907ec64d0317d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.