Triple
T36917073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Tech vs Michigan State |
E913071
|
entity |
| Predicate | MichiganStateThreePointFieldGoals |
P176419
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Texas Tech vs Michigan State, MichiganStateThreePointFieldGoals, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MichiganStateThreePointFieldGoals Context triple: [Texas Tech vs Michigan State, MichiganStateThreePointFieldGoals, 7]
-
A.
MichiganStateFieldGoalPercentage
Indicates the percentage of field goal attempts successfully made by Michigan State in a given context (e.g., game or season).
-
B.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
C.
Michigan StateLeadingScorer
Indicates that the subject is the leading scorer for the Michigan State team in a given season or context.
-
D.
threePointFieldGoalsMade
chosen
Indicates the number of successful three-point field goals a player or team has made.
-
E.
MVPThreePointersAttempted
Indicates the number of three-point shots attempted by the MVP in a given context or period.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:13 p.m.