Triple
T3652806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC West |
E77459
|
entity |
| Predicate | playoffEligibility |
P28814
|
FINISHED |
| Object | FBS bowl games |
—
|
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: FBS bowl games | Statement: [SEC West, playoffEligibility, FBS bowl games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffEligibility Context triple: [SEC West, playoffEligibility, FBS bowl games]
-
A.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
B.
playoffParticipation
Indicates that an entity takes part in a postseason playoff competition within a given league or tournament.
-
C.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
D.
usedForPlayoffQualification
Indicates that something serves as a basis or criterion for determining whether a team qualifies for the playoffs.
-
E.
hasPostseasonAccess
chosen
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b805a48190a7bc230a382365d6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.