Triple
T34982156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulan |
E1008842
|
entity |
| Predicate | hasDiseaseContext |
P147387
|
FINISHED |
| Object | the Phage |
—
|
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: the Phage | Statement: [Sulan, hasDiseaseContext, the Phage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiseaseContext Context triple: [Sulan, hasDiseaseContext, the Phage]
-
A.
diseaseContext
chosen
Indicates that the relationship or action occurs within, is influenced by, or is specifically relevant to a particular disease or pathological condition.
-
B.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
C.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
D.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
E.
includesDisease
Indicates that one entity (such as a category, group, or collection) contains or encompasses a particular disease as part of its members or elements.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4:01 p.m.