Triple
T3242823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguars–Titans rivalry |
E68000
|
entity |
| Predicate | fanBaseEmotion |
P6226
|
FINISHED |
| Object | strong dislike between fan bases |
—
|
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: strong dislike between fan bases | Statement: [Jaguars–Titans rivalry, fanBaseEmotion, strong dislike between fan bases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseEmotion Context triple: [Jaguars–Titans rivalry, fanBaseEmotion, strong dislike between fan bases]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
C.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
D.
fanbaseCharacteristic
chosen
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
E.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf17463481909447f6ab46016407 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.