Triple
T35216628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCRmy |
E1016830
|
entity |
| Predicate | hasSubcultureElements |
P3114
|
FINISHED |
| Object | emo fashion |
—
|
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: emo fashion | Statement: [MCRmy, hasSubcultureElements, emo fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureElements Context triple: [MCRmy, hasSubcultureElements, emo fashion]
-
A.
hasSubcultureStatus
Indicates that an entity holds a particular role, recognition, or standing within a specific subculture or subcultural context.
-
B.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
C.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
D.
hasCulturalCore
Indicates that one entity embodies or provides the central cultural values, practices, or identity that fundamentally define another entity.
-
E.
hasUltrasCulture
Indicates that a group, organization, or entity maintains an organized, passionate supporter subculture typically associated with "ultras" fan traditions.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 3, 2026, 4:02 p.m.