Triple
T920077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central League |
E19861
|
entity |
| Predicate | decidesJapanSeriesRepresentativeBy |
P22385
|
FINISHED |
| Object | league champion |
—
|
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: league champion | Statement: [Central League, decidesJapanSeriesRepresentativeBy, league champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesJapanSeriesRepresentativeBy Context triple: [Central League, decidesJapanSeriesRepresentativeBy, league champion]
-
A.
JapanSeriesTitle
Indicates that the given title is the name used for a series in Japan.
-
B.
decisiveGamePitcher
Indicates that the pitcher played in the decisive game that determined the outcome of a series or championship.
-
C.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
D.
JapanSeriesTitles
Indicates that the subject is a title belonging to a series originating from or specifically released in Japan.
-
E.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.