Triple
T27806642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seibel 5656 |
E702394
|
entity |
| Predicate | belongsToBreedingProgram |
P16656
|
FINISHED |
| Object | Seibel hybrid grape program |
—
|
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: Seibel hybrid grape program | Statement: [Seibel 5656, belongsToBreedingProgram, Seibel hybrid grape program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToBreedingProgram Context triple: [Seibel 5656, belongsToBreedingProgram, Seibel hybrid grape program]
-
A.
hasBreedingProgram
Indicates that an entity operates, participates in, or maintains an organized program for breeding organisms (such as animals or plants).
-
B.
belongsToProgram
chosen
Indicates that an entity is a member of, or is associated with, a specific program.
-
C.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
D.
belongsToBreedGroup
Indicates that an animal is classified as a member of a specific breed group.
-
E.
breedingAssociation
Indicates a relationship where entities are associated for the purpose of breeding or reproduction.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 5:39 p.m.