Triple
T36917072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Tech vs Michigan State |
E913071
|
entity |
| Predicate | TexasTechThreePointFieldGoals |
P176419
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Texas Tech vs Michigan State, TexasTechThreePointFieldGoals, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TexasTechThreePointFieldGoals Context triple: [Texas Tech vs Michigan State, TexasTechThreePointFieldGoals, 9]
-
A.
TexasTechFieldGoalPercentage
Indicates the percentage of field goal attempts successfully made by Texas Tech in a given context (such as a game or season).
-
B.
threePointFieldGoalsMade
chosen
Indicates the number of successful three-point field goals a player or team has made.
-
C.
TexasTechCoach
Indicates that one entity serves as a coach for the Texas Tech athletic program.
-
D.
MVPThreePointersAttempted
Indicates the number of three-point shots attempted by the MVP in a given context or period.
-
E.
careerThreePointPercentage
Indicates the proportion of three-point shots a player has successfully made over the entire span of their career.
- 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.