Triple
T36917117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia vs Texas Tech |
E913072
|
entity |
| Predicate | TexasTechRegulationScore |
P47874
|
FINISHED |
| Object | 68 |
—
|
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: 68 | Statement: [Virginia vs Texas Tech, TexasTechRegulationScore, 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TexasTechRegulationScore Context triple: [Virginia vs Texas Tech, TexasTechRegulationScore, 68]
-
A.
TexasTechSeed
Indicates a seeding or ranking assignment related to Texas Tech in a competitive context (such as a tournament or bracket).
-
B.
GreeneRank
Indicates a ranking or ordered position assigned according to Greene’s specific criteria or system.
-
C.
regulationScore
chosen
Indicates the degree or quality of how well something is controlled, managed, or kept within desired limits.
-
D.
regulatedInstitution
Indicates that one entity is an institution whose activities are subject to oversight, control, or rules imposed by another entity or authority.
-
E.
lawSchoolRankingContext
Indicates the contextual ranking information associated with a law school, such as its position or status within a specified ranking system or timeframe.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:13 p.m.