Triple
T8789907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madiran wine region |
E209135
|
entity |
| Predicate | winemakingPractice |
P77755
|
FINISHED |
| Object | often uses oak aging |
—
|
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: often uses oak aging | Statement: [Madiran wine region, winemakingPractice, often uses oak aging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winemakingPractice Context triple: [Madiran wine region, winemakingPractice, often uses oak aging]
-
A.
vinificationUse
chosen
Indicates the process or method of winemaking applied to a given wine or batch.
-
B.
vinification
Indicates the process by which grapes (or other fruits) are transformed into wine through fermentation and related winemaking steps.
-
C.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
-
D.
wineLaw
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
E.
traditionalVinification
Indicates that a wine is produced using traditional or historically established winemaking methods rather than modern or industrial techniques.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8d25f881908863d636fa57a8a2 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.