Triple
T37988946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Dantonio |
E947771
|
entity |
| Predicate | overallRecordAtMichiganState |
P189829
|
FINISHED |
| Object | 114–57 |
—
|
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: 114–57 | Statement: [Mark Dantonio, overallRecordAtMichiganState, 114–57]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overallRecordAtMichiganState Context triple: [Mark Dantonio, overallRecordAtMichiganState, 114–57]
-
A.
overallRecordAtMichigan
Indicates the overall win-loss (and possibly tie) record that an entity has achieved while at Michigan.
-
B.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
C.
overallRecordAtOhioState
Indicates the overall performance record (such as wins and losses) associated with something in the context of Ohio State.
-
D.
bowlRecordAtMichigan
Indicates that a team or individual has a recorded performance or participation in bowl games specifically while associated with Michigan.
-
E.
Michigan StateLeadingScorer
Indicates that the subject is the leading scorer for the Michigan State team in a given season or context.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.