Triple
T15383410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peaches (song) |
E367859
|
entity |
| Predicate | viralStatus |
P66008
|
FINISHED |
| Object | viral hit |
—
|
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: viral hit | Statement: [Peaches (song), viralStatus, viral hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viralStatus Context triple: [Peaches (song), viralStatus, viral hit]
-
A.
hasViralImpact
Indicates that an entity causes, contributes to, or is associated with rapid, wide-scale spread or influence, similar to how viral content propagates.
-
B.
usesViralVector
Indicates that one entity employs a viral vector as a delivery mechanism or tool to introduce genetic material or components into another entity.
-
C.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
D.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
E.
spreadingStatus
chosen
Indicates the current state or progression of how something is spreading or being disseminated (e.g., whether and how it is expanding, stable, or declining).
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.