Triple
T38641200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collie eye anomaly |
E938597
|
entity |
| Predicate | causativeGene |
P149311
|
FINISHED |
| Object | NHEJ1 |
—
|
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: NHEJ1 | Statement: [Collie eye anomaly, causativeGene, NHEJ1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causativeGene Context triple: [Collie eye anomaly, causativeGene, NHEJ1]
-
A.
isPrimaryGeneticCauseOf
chosen
Indicates that one genetic factor is the main or predominant cause responsible for producing a particular condition, trait, or outcome.
-
B.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
C.
geneticFindings
Indicates that there is information describing observed genetic variants, mutations, or other genomic characteristics identified in an entity.
-
D.
geneticallyLinkedTo
Indicates a relationship where two entities share a genetic connection, such as common ancestry, shared genes, or hereditary association.
-
E.
protectiveAlleleForDisease
Indicates that the presence of a specific allele reduces the risk, severity, or likelihood of developing a particular disease.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.