Triple
T25336429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catawba |
E635290
|
entity |
| Predicate | grapeSpeciesHybridOf |
P80117
|
FINISHED |
| Object | Vitis labrusca × Vitis vinifera |
—
|
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: Vitis labrusca × Vitis vinifera | Statement: [Catawba, grapeSpeciesHybridOf, Vitis labrusca × Vitis vinifera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeSpeciesHybridOf Context triple: [Catawba, grapeSpeciesHybridOf, Vitis labrusca × Vitis vinifera]
-
A.
grapeParentage
chosen
Indicates the parent-offspring relationship between grape varieties, specifying which grape(s) are the progenitors of another grape.
-
B.
grapeFamily
Indicates that one entity belongs to, or is classified within, the same botanical family as grapes.
-
C.
grapeVarietyType
Indicates the specific type or classification of a grape variety used or referred to in a given context.
-
D.
grapeVarietyScientificName
Indicates the scientific (Latin) name assigned to a specific grape variety.
-
E.
linkedGrapeVariety
Indicates that there is an established relationship or association between one grape variety and another (or related grape variety 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:32 p.m.