Triple
T36917119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia vs Texas Tech |
E913072
|
entity |
| Predicate | TexasTechOvertimeScore |
P190095
|
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: [Virginia vs Texas Tech, TexasTechOvertimeScore, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TexasTechOvertimeScore Context triple: [Virginia vs Texas Tech, TexasTechOvertimeScore, 9]
-
A.
TexasTechCoach
Indicates that one entity serves as a coach for the Texas Tech athletic program.
-
B.
TexasTechFieldGoalPercentage
Indicates the percentage of field goal attempts successfully made by Texas Tech in a given context (such as a game or season).
-
C.
game7Overtimes
Indicates that a game extended into a seventh overtime period, reflecting an exceptionally prolonged and closely contested match.
-
D.
VirginiaOvertimeScore
Indicates that the score represents Virginia’s points earned during an overtime period in a game or match.
-
E.
OklahomaScore
Indicates that a score or number of points is associated with Oklahoma in a particular context or event.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.