Triple
T36917127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia vs Texas Tech |
E913072
|
entity |
| Predicate | TexasTechFirstTitleGameAppearance |
P190396
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Virginia vs Texas Tech, TexasTechFirstTitleGameAppearance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TexasTechFirstTitleGameAppearance Context triple: [Virginia vs Texas Tech, TexasTechFirstTitleGameAppearance, true]
-
A.
TexasTechOvertimeScore
Indicates the number of points Texas Tech scored during the overtime period of a game.
-
B.
TexasTechCoach
Indicates that one entity serves as a coach for the Texas Tech athletic program.
-
C.
TexasTechSeed
Indicates a seeding or ranking assignment related to Texas Tech in a competitive context (such as a tournament or bracket).
-
D.
TexasTechFieldGoalPercentage
Indicates the percentage of field goal attempts successfully made by Texas Tech in a given context (such as a game or season).
-
E.
TexasTechAdvancement
Indicates that one entity is advancing, promoting, or contributing to the progress, development, or support of Texas Tech.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:13 p.m.