Triple
T12351200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Low |
E294489
|
entity |
| Predicate | isPopularOn |
P104296
|
FINISHED |
| Object | streaming platforms |
—
|
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: streaming platforms | Statement: [On the Low, isPopularOn, streaming platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularOn Context triple: [On the Low, isPopularOn, streaming platforms]
-
A.
isPopularAt
chosen
Indicates that an entity enjoys a high level of recognition, approval, or favor within a specified place, context, or time.
-
B.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
C.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
D.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
E.
hasPopularityCharacteristic
Indicates that an entity possesses a particular attribute or quality related to its level or type of popularity.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7cbff08190849cd2aec4ce3243 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.