Triple
T19123481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 New York Yankees season |
E468109
|
entity |
| Predicate | qualifiedForPostseason |
P78194
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1980 New York Yankees season, qualifiedForPostseason, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedForPostseason Context triple: [1980 New York Yankees season, qualifiedForPostseason, true]
-
A.
hasPostseasonAccess
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
-
B.
madePostseason
chosen
Indicates that an individual or team successfully qualified for and participated in the postseason phase of a competition or league.
-
C.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
D.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
E.
playedInPostseasonFor
Indicates that an athlete participated in postseason games or competitions as a member of a specified team or organization.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cae37c81908692c7f83671229f |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.