Triple
T34957858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lifesigns |
E1008166
|
entity |
| Predicate | featuresMedicalCondition |
P129457
|
FINISHED |
| Object | 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: Phage | Statement: [Lifesigns, featuresMedicalCondition, Phage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMedicalCondition Context triple: [Lifesigns, featuresMedicalCondition, Phage]
-
A.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
B.
clinicalCondition
chosen
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other entity.
-
C.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
D.
depictsMedicalCondition
Indicates that one entity visually represents or illustrates a particular medical condition affecting another entity or subject.
-
E.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.