Triple
T18936274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Côme blanc |
E463254
|
entity |
| Predicate | cultivarType |
P75433
|
FINISHED |
| Object | Vitis vinifera grape variety |
—
|
LITERAL FINISHED |
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 vinifera grape variety | Statement: [Saint-Côme blanc, cultivarType, Vitis vinifera grape variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultivarType Context triple: [Saint-Côme blanc, cultivarType, Vitis vinifera grape variety]
-
A.
cultivationType
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
-
B.
cultivarName
chosen
Indicates that a specific cultivated variety (cultivar) is designated by a particular name.
-
C.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
D.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
E.
cultivarOrigin
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e7b87c81909dc29defb33c8e00 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.