Triple
T28386767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIV-1 |
E719039
|
entity |
| Predicate | usesCoreceptor |
P177537
|
FINISHED |
| Object | CCR5 |
—
|
NE NERFINISHED |
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: CCR5 | Statement: [HIV-1, usesCoreceptor, CCR5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoreceptor Context triple: [HIV-1, usesCoreceptor, CCR5]
-
A.
usedAsConsortsIn
Indicates that the entities served in the role of consorts within a specified context, such as a reign, period, or relationship.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
usedWithSubunit
Indicates that one entity is employed, operated, or functions in conjunction with a specific subunit of another entity.
-
D.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
E.
possibleCoregentWith
Indicates that two individuals could have ruled simultaneously as co-regents or shared sovereign authority during an overlapping period.
- F. None of above. chosen
Provenance (4 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 28, 2026, 1:10 a.m.