Triple
T29068581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dura |
E735751
|
entity |
| Predicate | hasSocialMediaTrend |
P145540
|
FINISHED |
| Object | #DuraChallenge |
—
|
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: #DuraChallenge | Statement: [Dura, hasSocialMediaTrend, #DuraChallenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialMediaTrend Context triple: [Dura, hasSocialMediaTrend, #DuraChallenge]
-
A.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
socialMediaTrend
chosen
Indicates that something is currently popular, widely discussed, or rapidly spreading in visibility and engagement on social media platforms.
-
C.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
D.
hasOnlineTrendType
Indicates that an entity is associated with a specific category or type of online trend.
-
E.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 10:19 a.m.