Triple
T3378640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's a Sin |
E71125
|
entity |
| Predicate | inspiredPublicDiscussionOn |
P9239
|
FINISHED |
| Object | HIV testing |
—
|
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: HIV testing | Statement: [It's a Sin, inspiredPublicDiscussionOn, HIV testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredPublicDiscussionOn Context triple: [It's a Sin, inspiredPublicDiscussionOn, HIV testing]
-
A.
influencedDiscussionOf
chosen
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
B.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
C.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
D.
inspiredOppositionFrom
Indicates that one entity’s actions, ideas, or existence motivated another entity to form or express opposition against it.
-
E.
inspiredDevelopmentOf
Indicates that one entity served as a motivating influence or creative stimulus leading to the development or creation of another entity.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2eacb5c81908071a1dacc9a897a |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.