Triple
T37856129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 NCAA Division I-A football national championship |
E944194
|
entity |
| Predicate | notableRegularSeasonOpponent |
P12651
|
FINISHED |
| Object | Miami Hurricanes |
E118233
|
NE 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: Miami Hurricanes | Statement: [1988 NCAA Division I-A football national championship, notableRegularSeasonOpponent, Miami Hurricanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegularSeasonOpponent Context triple: [1988 NCAA Division I-A football national championship, notableRegularSeasonOpponent, Miami Hurricanes]
-
A.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
B.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
C.
hasRegularSeasonGamesAgainst
chosen
Indicates that one team or participant plays scheduled, recurring competitive games against another during the regular season.
-
D.
recordOpponent
Indicates that one entity is documented or registered as the opposing party or competitor of another entity.
-
E.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
- F. None of above.
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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb9808f8819083c247861d1c4cd2 |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.