Triple
T9099498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheingau |
E218115
|
entity |
| Predicate | majorGrape |
P975
|
FINISHED |
| Object | Riesling |
—
|
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: Riesling | Statement: [Rheingau, majorGrape, Riesling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorGrape Context triple: [Rheingau, majorGrape, Riesling]
-
A.
primaryGrapeVariety
chosen
Indicates that one entity is the main or predominant grape variety used in producing the other entity (typically a wine or wine-based product).
-
B.
traditionalGrapeVariety
Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
-
C.
secondaryGrape
Indicates that one grape variety serves as a secondary or supporting component in a wine blend relative to the primary grape.
-
D.
grapeParentage
Indicates the parent-offspring relationship between grape varieties, specifying which grape(s) are the progenitors of another grape.
-
E.
primaryGrapeUse
Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9710ac04819096b9c8d3399b9c35 |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.