Triple
T22837703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korean |
E565990
|
entity |
| Predicate | associatedWithPopularCulture |
P16088
|
FINISHED |
| Object | K-pop |
—
|
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: K-pop | Statement: [South Korean, associatedWithPopularCulture, K-pop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPopularCulture Context triple: [South Korean, associatedWithPopularCulture, K-pop]
-
A.
inPopularCulture
chosen
Indicates that an entity is referenced, depicted, or otherwise present within works or discussions of popular culture.
-
B.
popularCultureStatus
Indicates the degree to which something is recognized, influential, or prominent within mainstream popular culture.
-
C.
cultPopularFrom
Indicates that something has gained or exhibits cult popularity originating from a particular source, context, or group.
-
D.
popularCultureTrait
Indicates that an entity exhibits a characteristic, behavior, or element that is commonly recognized or influential within popular culture.
-
E.
associatedDecadeInPopCulture
Indicates the decade in popular culture with which an entity is most closely linked or commonly recognized.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e303cec81909c5c118dc8c93354 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.