Triple
T33278915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAC East Division |
E851982
|
entity |
| Predicate | tieBreakerForChampionship |
P6631
|
FINISHED |
| Object | MAC football tiebreaker rules |
—
|
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: MAC football tiebreaker rules | Statement: [MAC East Division, tieBreakerForChampionship, MAC football tiebreaker rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakerForChampionship Context triple: [MAC East Division, tieBreakerForChampionship, MAC football tiebreaker rules]
-
A.
tieBreakerAppointedBy
Indicates that a specific party or authority is responsible for appointing the individual or entity who will act as the tie-breaker in a decision-making process.
-
B.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
C.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
-
D.
tieBreakerMetric
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
E.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.