Triple
T20112419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystik Spiral |
E490365
|
entity |
| Predicate | hasFanBaseInFiction |
P48181
|
FINISHED |
| Object | small cult following |
—
|
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: small cult following | Statement: [Mystik Spiral, hasFanBaseInFiction, small cult following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanBaseInFiction Context triple: [Mystik Spiral, hasFanBaseInFiction, small cult following]
-
A.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
-
B.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
C.
hasFanCommunity
chosen
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
D.
hasCustomerBaseInFiction
Indicates that an entity’s primary or significant group of customers exists within fictional works or fictional contexts.
-
E.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e21f908190b46c747662ff378a |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.