Triple
T36571689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hepatitis C virus |
E902136
|
entity |
| Predicate | hasGenotype |
P195843
|
FINISHED |
| Object | genotype 1 |
—
|
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: genotype 1 | Statement: [hepatitis C virus, hasGenotype, genotype 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenotype Context triple: [hepatitis C virus, hasGenotype, genotype 1]
-
A.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
B.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
C.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
D.
hasGeneticComponent
Indicates that the associated condition, trait, or phenomenon is influenced or determined in part by genetic factors.
-
E.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.