Triple
T22984950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy War (Utah–BYU rivalry) |
E571579
|
entity |
| Predicate | fanTraditionContext |
P150497
|
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: [Holy War (Utah–BYU rivalry), fanTraditionContext, tailgating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanTraditionContext Context triple: [Holy War (Utah–BYU rivalry), fanTraditionContext, tailgating]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBase1
Indicates that one entity serves as the primary or original fan base supporting another entity.
-
C.
fanbaseCharacteristic
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
D.
fanOfSport
Indicates that a person supports, follows, or has a strong interest in a particular sport.
-
E.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
- F. None of above. chosen
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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18298637c819086fca34d55bad22d |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.