Triple
T11065683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Card Series |
E261615
|
entity |
| Predicate | byeTeams |
P85421
|
FINISHED |
| Object | top two division winners in each league |
—
|
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: top two division winners in each league | Statement: [Wild Card Series, byeTeams, top two division winners in each league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: byeTeams Context triple: [Wild Card Series, byeTeams, top two division winners in each league]
-
A.
byeTeamsPerConference
Indicates the number of teams in each conference that receive a bye (i.e., skip a round) in a competition or playoff structure.
-
B.
stateTeam
Indicates that a team is officially associated with, represents, or belongs to a particular state.
-
C.
eligibleTeamsFrom
chosen
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
awayTeam
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7991f84488190a974d1744a62798d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.