Triple
T20818591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic Dance |
E512509
|
entity |
| Predicate | hasFandomMemeStatus |
P66537
|
FINISHED |
| Object | internet culture |
—
|
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: internet culture | Statement: [Magic Dance, hasFandomMemeStatus, internet culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomMemeStatus Context triple: [Magic Dance, hasFandomMemeStatus, internet culture]
-
A.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
B.
hasMemeFormat
Indicates that one entity serves as the template or structural pattern used to create memes involving another entity.
-
C.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
D.
associatedMeme
chosen
Indicates that one entity is linked or connected to another entity in the context of a meme (e.g., as its related or corresponding meme).
-
E.
hasFandomWithinStory
Indicates that within the narrative of a story, one entity is a fan or admirer of another entity (such as a character, group, or work) that exists inside that same story world.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f5b1e08190a9c26f76bd544b68 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.