Triple
T22727616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big 12 Coach of the Year |
E562038
|
entity |
| Predicate | usesCompetition |
P149478
|
FINISHED |
| Object | Big 12 Conference football schedule |
—
|
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: Big 12 Conference football schedule | Statement: [Big 12 Coach of the Year, usesCompetition, Big 12 Conference football schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCompetition Context triple: [Big 12 Coach of the Year, usesCompetition, Big 12 Conference football schedule]
-
A.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
B.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
-
C.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
-
D.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
E.
usedInCompetitionContext
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
- F. None of above. chosen
Provenance (4 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792b22cc819099aa00bb2dbacce3 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:21 p.m.