Triple
T6001853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Valley Conference |
E133615
|
entity |
| Predicate | sponsoredFootball |
P790
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Missouri Valley Conference, sponsoredFootball, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredFootball Context triple: [Missouri Valley Conference, sponsoredFootball, false]
-
A.
sportsSponsored
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
B.
postFootballUse
Indicates that something is used or occurs after playing or participating in football.
-
C.
sponsorSport
chosen
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
D.
playedAssociationFootball
Indicates that an entity has participated in playing the sport of association football (soccer).
-
E.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee7c0e08190a6e78969448b070a |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.