Triple
T33278904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAC East Division |
E851982
|
entity |
| Predicate | includesBowlEligibleTeams |
P85421
|
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: [MAC East Division, includesBowlEligibleTeams, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBowlEligibleTeams Context triple: [MAC East Division, includesBowlEligibleTeams, yes]
-
A.
eligibleTeamsFrom
chosen
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
B.
footballBowlParticipation
Indicates that an entity (typically a team or player) took part in a specific football bowl game.
-
C.
hasBowlGameType
Indicates that an entity’s associated bowl game is of a specified type or category.
-
D.
isMajorBowlGame
Indicates that a particular football game qualifies as one of the most prominent, high-profile postseason bowl games.
-
E.
usesNCAAEligibilityRules
Indicates that an entity applies or follows NCAA eligibility rules to determine whether individuals are allowed to participate in NCAA-governed activities.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0301c45274819083b0dd9d335f7ee0 |
completed | May 12, 2026, 10:32 a.m. |
| PD | Predicate disambiguation | batch_6a03015c272481908a7bfe81befb1764 |
completed | May 12, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:32 a.m.