Triple
T15527655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rueda DO |
E369122
|
entity |
| Predicate | grapeRequirementForRuedaVerdejoSuperior |
P91947
|
FINISHED |
| Object | minimum 100% Verdejo |
—
|
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: minimum 100% Verdejo | Statement: [Rueda DO, grapeRequirementForRuedaVerdejoSuperior, minimum 100% Verdejo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeRequirementForRuedaVerdejoSuperior Context triple: [Rueda DO, grapeRequirementForRuedaVerdejoSuperior, minimum 100% Verdejo]
-
A.
grapeCondition
Indicates the state or quality of a grape, such as its health, ripeness, or any notable physical condition.
-
B.
grapeProduct
Indicates that one entity is a product derived from or made using grapes.
-
C.
grapeMinimum
Indicates the minimum quantity, size, or threshold value associated with grapes in a given context.
-
D.
dominantGrapePercentageRequirement
chosen
Indicates the minimum percentage of a single grape variety that must be present in a wine for it to be considered dominant or to meet a specific labeling or classification rule.
-
E.
redWineRequired
Indicates that red wine is needed or mandated in the given context or situation.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.