Triple
T31572395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 27th World Series |
E805599
|
entity |
| Predicate | leagueOpponentLeague |
P176774
|
FINISHED |
| Object | National League |
—
|
NE NERFINISHED |
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: National League | Statement: [27th World Series, leagueOpponentLeague, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueOpponentLeague Context triple: [27th World Series, leagueOpponentLeague, National League]
-
A.
rivalLeague
Indicates that two leagues are in competition with each other, typically vying for similar audiences, resources, or status.
-
B.
oppositeLeaguePennant
Indicates that two baseball teams have won league pennants in opposing leagues (e.g., American League vs. National League) in the same season or corresponding context.
-
C.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
D.
playoffOpponent
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
E.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
- F. None of above. chosen
Provenance (4 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 30, 2026, 10:20 p.m.