Triple
T19222614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinomavro |
E480655
|
entity |
| Predicate | oakAgeingSuitability |
P87418
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Xinomavro, oakAgeingSuitability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oakAgeingSuitability Context triple: [Xinomavro, oakAgeingSuitability, high]
-
A.
oakAgingTypical
chosen
Indicates that it is typical or customary for something (such as a product, especially a beverage) to undergo aging in oak.
-
B.
wineAgeingPotential
Indicates the capacity or suitability of a wine to improve in quality or maintain desirable characteristics over time with proper aging.
-
C.
vineAge
Indicates the age or length of time that a vine has been growing or established.
-
D.
oakTypeUsed
Indicates that a particular type of oak is used in relation to another entity, such as in construction, manufacturing, or production.
-
E.
wineAgeingPreference
Indicates a preference for how long wine should be aged before consumption or use.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa94aed081909045cfed8edc6039 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.