Triple
T1119424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Bowl |
E11175
|
entity |
| Predicate | traditionalMatchup |
P10212
|
FINISHED |
| Object | Big Ten vs. Pac-12 |
—
|
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: Big Ten vs. Pac-12 | Statement: [Rose Bowl, traditionalMatchup, Big Ten vs. Pac-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMatchup Context triple: [Rose Bowl, traditionalMatchup, Big Ten vs. Pac-12]
-
A.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
-
B.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
C.
matchType
chosen
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
D.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
E.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.