Triple
T35306992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UW–WSU rivalry |
E1019663
|
entity |
| Predicate | fanBaseUW |
P897
|
FINISHED |
| Object | Husky fans |
—
|
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: Husky fans | Statement: [UW–WSU rivalry, fanBaseUW, Husky fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseUW Context triple: [UW–WSU rivalry, fanBaseUW, Husky fans]
-
A.
fanBase
chosen
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.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
D.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
-
E.
FAcupUpsetSeason
Indicates that, in a given season, an FA Cup match resulted in an upset where a lower-ranked or underdog team defeated a higher-ranked or favored opponent.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904fd0248190899e6266e3a6b023 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.