Triple
T36979177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toro Denominación de Origen wine |
E914776
|
entity |
| Predicate | typicalVineAge |
P41717
|
FINISHED |
| Object | often old vines |
—
|
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 old vines | Statement: [Toro Denominación de Origen wine, typicalVineAge, often old vines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVineAge Context triple: [Toro Denominación de Origen wine, typicalVineAge, often old vines]
-
A.
vineAge
chosen
Indicates the age or length of time that a vine has been growing or established.
-
B.
typicalVineTraining
Indicates that one entity is the standard or commonly used method of training or shaping the growth of another entity, typically in a vine or climbing context.
-
C.
VineAcquisitionYear
Indicates the year in which a vine was acquired or obtained.
-
D.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
E.
maturityRange
Indicates the span or limits of maturity (such as age, development stage, or readiness) within which the related entities or conditions are considered applicable.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.