Triple
T29165766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 Major League Baseball season |
E739312
|
entity |
| Predicate | wildCardUsedInPostseason |
P156792
|
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: [1995 Major League Baseball season, wildCardUsedInPostseason, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildCardUsedInPostseason Context triple: [1995 Major League Baseball season, wildCardUsedInPostseason, true]
-
A.
madePostseason
Indicates that an individual or team successfully qualified for and participated in the postseason phase of a competition or league.
-
B.
wildCardStanding
Indicates that an entity holds a wildcard position or qualification status within a ranking, bracket, or selection process.
-
C.
hasWildCardTeams
chosen
Indicates that certain teams qualify for a competition or playoff through wild card spots rather than standard qualification criteria.
-
D.
wildCardGameALLoser
Indicates that an entity is the loser of a wild card game in an all-encompassing or overall context.
-
E.
postSeasonUse
Indicates that an entity is used or active during a post-season period following a regular season or main event.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d4efc88190a18d80abadc96faf |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:49 a.m.