Triple
T35412294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghemme DOCG |
E1023544
|
entity |
| Predicate | principalGrape |
P975
|
FINISHED |
| Object | Nebbiolo |
—
|
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: Nebbiolo | Statement: [Ghemme DOCG, principalGrape, Nebbiolo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalGrape Context triple: [Ghemme DOCG, principalGrape, Nebbiolo]
-
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.
primaryGrapeFamily
Indicates that one grape variety belongs to, or is classified under, a broader primary grape family.
-
C.
primaryGrapeUse
Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
-
D.
secondaryGrape
Indicates that one grape variety serves as a secondary or supporting component in a wine blend relative to the primary grape.
-
E.
grapeVarietal
Indicates that one entity is a specific type or variety of grape used in wine or grape production in relation to another 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.