Triple
T11166389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need to Know |
E264169
|
entity |
| Predicate | hasViralSuccess |
P83536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Need to Know, hasViralSuccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViralSuccess Context triple: [Need to Know, hasViralSuccess, true]
-
A.
wentViralOn
Indicates that content rapidly spread and gained widespread attention or popularity on a particular platform or medium.
-
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.
hasNotableSuccessIn
chosen
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
D.
followsViralDebutOfArtistWith
Indicates that one event, release, or action occurs after and in response to the viral debut of an artist, in association with a specified other entity.
-
E.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e88843cc81909e503f0921c6d297 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.