Triple
T25627229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan White Part D |
E642465
|
entity |
| Predicate | healthArea |
P134642
|
FINISHED |
| Object | HIV/AIDS |
—
|
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/AIDS | Statement: [Ryan White Part D, healthArea, HIV/AIDS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthArea Context triple: [Ryan White Part D, healthArea, HIV/AIDS]
-
A.
hasHealthArea
chosen
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
-
B.
healthTheme
Indicates that the subject is associated with, focuses on, or is characterized by a particular health-related topic or theme.
-
C.
publicHealthDomain
Indicates that something is related to, situated within, or primarily concerned with the field of public health.
-
D.
healthAssociation
Indicates a relationship where one factor, condition, or entity is linked to an effect, outcome, or status related to health.
-
E.
healthAuthority
Indicates that an entity serves as an official body responsible for overseeing, regulating, or managing health-related matters for another entity or within a specific jurisdiction.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa248b6c8190b79173bc9d806f21 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:15 p.m.