Triple
T38641180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collie eye anomaly |
E938597
|
entity |
| Predicate | congenital |
P97656
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Collie eye anomaly, congenital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congenital Context triple: [Collie eye anomaly, congenital, true]
-
A.
congenitalFormAffects
chosen
Indicates that a congenital (present at birth) form or condition has an influence or impact on another related entity or outcome.
-
B.
conception
Indicates the event or process by which a new life or entity begins, typically through fertilization or the initiation of pregnancy.
-
C.
embryologicalFeature
Indicates a relationship where one entity is an anatomical or biological structure characterized or defined by its origin, development, or properties during the embryonic stage.
-
D.
developmentalContractedWith
Indicates a formal developmental agreement or contract established between two entities, typically for research, design, or product development activities.
-
E.
nonAcnegenic
Indicates that a product or substance does not cause or promote acne formation on the skin.
- 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.