Triple
T35862841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DO Vinos de Madrid |
E1036999
|
entity |
| Predicate | wineStyleIncludes |
P55208
|
FINISHED |
| Object | young wines |
—
|
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: young wines | Statement: [DO Vinos de Madrid, wineStyleIncludes, young wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineStyleIncludes Context triple: [DO Vinos de Madrid, wineStyleIncludes, young wines]
-
A.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
B.
wineStylesAssociatedWith
chosen
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
C.
wineStyleContribution
Indicates how much a given factor or component influences or shapes the overall style or character of a wine.
-
D.
wineVariety
Indicates the specific type or variety of wine associated with an entity.
-
E.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.