Triple
T36365598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saanen goat |
E895614
|
entity |
| Predicate | influencedBreed |
P117810
|
FINISHED |
| Object | Sable Saanen goat |
—
|
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: Sable Saanen goat | Statement: [Saanen goat, influencedBreed, Sable Saanen goat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedBreed Context triple: [Saanen goat, influencedBreed, Sable Saanen goat]
-
A.
influenceOnBreed
chosen
Indicates that one entity has an effect on the characteristics, development, or traits of a particular breed.
-
B.
breedsFrom
Indicates that one organism or entity is produced, derived, or propagated from another through breeding or reproductive processes.
-
C.
wasBredBy
Indicates that an entity (typically an animal or plant) was produced or developed through the breeding efforts or program of another entity (such as a breeder, organization, or facility).
-
D.
madeFromBreed
Indicates that something is produced or derived using a particular breed as its source or primary constituent.
-
E.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:10 p.m.