Triple
T122200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil War (Oregon–Oregon State football rivalry) |
E2471
|
entity |
| Predicate | hasFanTraditions |
P1114
|
FINISHED |
| Object | tailgating |
—
|
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: tailgating | Statement: [Civil War (Oregon–Oregon State football rivalry), hasFanTraditions, tailgating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanTraditions Context triple: [Civil War (Oregon–Oregon State football rivalry), hasFanTraditions, tailgating]
-
A.
culturalTradition
chosen
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
B.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
C.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
D.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
E.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a2573b4e7481909ee09d2899f8a74b |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.