Triple
T30753067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpington chicken |
E783006
|
entity |
| Predicate | createdFromBreed |
P106562
|
FINISHED |
| Object | Minorca |
—
|
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: Minorca | Statement: [Orpington chicken, createdFromBreed, Minorca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdFromBreed Context triple: [Orpington chicken, createdFromBreed, Minorca]
-
A.
madeFromBreed
chosen
Indicates that something is produced or derived using a particular breed as its source or primary constituent.
-
B.
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).
-
C.
breedsFrom
Indicates that one organism or entity is produced, derived, or propagated from another through breeding or reproductive processes.
-
D.
wasBredIn
Indicates that an organism or animal was raised or produced through breeding in a particular place or environment.
-
E.
bredWith
Indicates that one entity has been used to reproduce or mate with another entity, typically for the purpose of producing offspring.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 29, 2026, 8:39 p.m.