Triple
T27024233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIVMA |
E680742
|
entity |
| Predicate | topicOfGuidelines |
P161779
|
FINISHED |
| Object | opportunistic infections in HIV |
—
|
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: opportunistic infections in HIV | Statement: [HIVMA, topicOfGuidelines, opportunistic infections in HIV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicOfGuidelines Context triple: [HIVMA, topicOfGuidelines, opportunistic infections in HIV]
-
A.
topicOfGuidelines
chosen
Indicates that something serves as the subject or focus addressed by a set of guidelines.
-
B.
usesGuidelines
Indicates that one entity follows or applies a specified set of guidelines in performing an action or making decisions.
-
C.
relatedGuideline
Indicates that one guideline has a defined relationship or association with another guideline, such as being complementary, dependent, or otherwise contextually linked.
-
D.
notableGuideline
Indicates that something is recognized as an important or especially significant rule, principle, or recommended practice.
-
E.
hasGuideline
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 7:10 a.m.