Triple
T27902153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacchus |
E705663
|
entity |
| Predicate | breedingInstitution |
P133128
|
FINISHED |
| Object | Geilweilerhof Institute for Grape Breeding |
—
|
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: Geilweilerhof Institute for Grape Breeding | Statement: [Bacchus, breedingInstitution, Geilweilerhof Institute for Grape Breeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingInstitution Context triple: [Bacchus, breedingInstitution, Geilweilerhof Institute for Grape Breeding]
-
A.
breedingInstitutionType
Indicates the type or category of institution responsible for breeding organisms or animals.
-
B.
breedingCenter
chosen
Indicates a relationship where an entity serves as a facility or location dedicated to breeding or reproducing organisms.
-
C.
wasBredIn
Indicates that an organism or animal was raised or produced through breeding in a particular place or environment.
-
D.
breedingAssociation
Indicates a relationship where entities are associated for the purpose of breeding or reproduction.
-
E.
breedingFamily
Indicates that one entity belongs to or is part of the family group used for breeding or reproduction with the other entity.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:42 p.m.