Triple
T20112415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystik Spiral |
E490365
|
entity |
| Predicate | hasMerchandiseInFiction |
P45835
|
FINISHED |
| Object | band T-shirts |
—
|
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: band T-shirts | Statement: [Mystik Spiral, hasMerchandiseInFiction, band T-shirts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMerchandiseInFiction Context triple: [Mystik Spiral, hasMerchandiseInFiction, band T-shirts]
-
A.
hasFictionalProduct
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
B.
hasMerchandiseTieIn
chosen
Indicates that one entity has a commercial or promotional product or line (merchandise) that is directly tied to, branded with, or derived from another entity.
-
C.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
D.
usedInMerchandise
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
E.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
- 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.