Triple
T27912861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seyval blanc |
E705980
|
entity |
| Predicate | notableBreeder |
P24704
|
FINISHED |
| Object | Bertille Seyve |
—
|
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: Bertille Seyve | Statement: [Seyval blanc, notableBreeder, Bertille Seyve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBreeder Context triple: [Seyval blanc, notableBreeder, Bertille Seyve]
-
A.
breeder
chosen
Indicates that an entity is responsible for producing, raising, or propagating another entity, typically through controlled reproduction.
-
B.
notableHorseBred
Indicates that one entity is a notable horse that was bred by the other entity.
-
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.
notableBreedingColony
Indicates that an entity serves as a significant or well-known site where a particular species regularly breeds or nests.
-
E.
breedingEase
Indicates how easily or with how little difficulty one entity can successfully breed or reproduce with 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 27, 2026, 6:51 p.m.