Triple
T22727610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big 12 Coach of the Year |
E562038
|
entity |
| Predicate | winnerAnnouncedIn |
P149477
|
FINISHED |
| Object | postseason |
—
|
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: postseason | Statement: [Big 12 Coach of the Year, winnerAnnouncedIn, postseason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerAnnouncedIn Context triple: [Big 12 Coach of the Year, winnerAnnouncedIn, postseason]
-
A.
winnerAssociated
Indicates that there is a relevant connection or affiliation between a winner and another entity in the context of a particular event or competition.
-
B.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
winnerCreditedAs
Indicates the name or designation under which the winner is officially recorded or credited for a particular award, contest, or achievement.
-
E.
winnerRound
Indicates that an entity is the one who won a particular round in a multi-round event or competition.
- 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.