Triple
T2062873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIV/AIDS |
E45830
|
entity |
| Predicate | preventionMethod |
P31419
|
FINISHED |
| Object | condom use |
—
|
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: condom use | Statement: [HIV/AIDS, preventionMethod, condom use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preventionMethod Context triple: [HIV/AIDS, preventionMethod, condom use]
-
A.
worksToPrevent
Indicates an entity actively takes measures or engages in actions to stop, reduce, or avoid the occurrence or impact of another entity or condition.
-
B.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
C.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
D.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
E.
controlMeasure
chosen
Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d239b48190a9f303446cbe3aa6 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.