Triple
T38641172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collie eye anomaly |
E938597
|
entity |
| Predicate | typicalBreed |
P193935
|
FINISHED |
| Object | Rough Collie |
E52694
|
NE 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: Rough Collie | Statement: [Collie eye anomaly, typicalBreed, Rough Collie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBreed Context triple: [Collie eye anomaly, typicalBreed, Rough Collie]
-
A.
hasTypicalBreed
chosen
Indicates that an entity (such as an animal or pet) is associated with a breed that is considered standard or characteristic for its kind.
-
B.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
C.
isRecognizedAsBreed
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
-
D.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
E.
sameBreedAs
Indicates that two entities belong to the same breed or variety within a species.
- F. None of above.
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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41f45af5a881908409ee5a08270460 |
completed | June 29, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.