Triple
T568167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon–Oregon State football rivalry |
E13602
|
entity |
| Predicate | gameFrequency |
P12965
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Oregon–Oregon State football rivalry, gameFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameFrequency Context triple: [Oregon–Oregon State football rivalry, gameFrequency, annual]
-
A.
matchupFrequency
chosen
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
-
B.
gamesPlayed
Indicates the number or set of games that an entity has participated in or completed.
-
C.
gameLength
Indicates the duration or total length of a game, typically measured in time or turns.
-
D.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
E.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.