Triple
T38641182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collie eye anomaly |
E938597
|
entity |
| Predicate | primaryLesion |
P206593
|
FINISHED |
| Object | choroidal hypoplasia |
—
|
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: choroidal hypoplasia | Statement: [Collie eye anomaly, primaryLesion, choroidal hypoplasia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLesion Context triple: [Collie eye anomaly, primaryLesion, choroidal hypoplasia]
-
A.
primaryDisease
Indicates that a disease is the main or principal medical condition affecting an entity, as opposed to secondary or comorbid conditions.
-
B.
primarySites
Indicates the main or originating locations associated with an entity, often distinguishing them from secondary or related sites.
-
C.
primaryRecordingSite
Indicates the main anatomical or spatial location where a recording or measurement was originally captured.
-
D.
primarySymptom
Indicates that the related symptom is the main or most characteristic symptom associated with a condition, disease, or disorder.
-
E.
hasTypicalLesionSite
Indicates that a disease or condition is characteristically associated with lesions occurring at a particular anatomical site.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.