Triple
T19701140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPB regular season |
E473097
|
entity |
| Predicate | topTeamsQualifyForPlayoffs |
P11176
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NPB regular season, topTeamsQualifyForPlayoffs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topTeamsQualifyForPlayoffs Context triple: [NPB regular season, topTeamsQualifyForPlayoffs, yes]
-
A.
numberOfPlayoffTeams
Indicates the total count of teams that qualify for or participate in the playoffs within a given league or season.
-
B.
playoffQualification
chosen
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
C.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
-
D.
hasPlayoffBerths
Indicates that an entity has qualified for the playoffs a specified number of times or in specified seasons.
-
E.
byeTeamsPerConference
Indicates the number of teams in each conference that receive a bye (i.e., skip a round) in a competition or playoff structure.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b667908190841bb5fb7bfdb3f7 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.