Triple
T37856117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 NCAA Division I-A football national championship |
E944194
|
entity |
| Predicate | bowlOpponent |
P7416
|
FINISHED |
| Object | West Virginia Mountaineers |
—
|
NE NERFINISHED |
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: West Virginia Mountaineers | Statement: [1988 NCAA Division I-A football national championship, bowlOpponent, West Virginia Mountaineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlOpponent Context triple: [1988 NCAA Division I-A football national championship, bowlOpponent, West Virginia Mountaineers]
-
A.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
-
B.
playoffOpponent
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
C.
teamOpposed
Indicates that one team is in opposition or conflict with another team, such as being rivals or competing against each other.
-
D.
finalOpponentTeam
chosen
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
E.
recordOpponent
Indicates that one entity is documented or registered as the opposing party or competitor of another entity.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.