Triple
T36917078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Tech vs Michigan State |
E913071
|
entity |
| Predicate | MichiganStateLeadingScorer |
P149568
|
FINISHED |
| Object | Cassius Winston |
—
|
NE NERFINISHED |
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: Cassius Winston | Statement: [Texas Tech vs Michigan State, MichiganStateLeadingScorer, Cassius Winston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MichiganStateLeadingScorer Context triple: [Texas Tech vs Michigan State, MichiganStateLeadingScorer, Cassius Winston]
-
A.
Michigan StateLeadingScorer
chosen
Indicates that the subject is the leading scorer for the Michigan State team in a given season or context.
-
B.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
C.
Michigan StateCoach
Indicates that a person holds or has held the position of head coach for a Michigan State University sports team.
-
D.
teamNicknameMichiganState
Indicates that a given nickname is used as the team nickname for Michigan State.
-
E.
mostPointsPerGamePlayer
Indicates the player who has the highest average number of points scored per game within a given context or season.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:13 p.m.