Triple
T24909105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viura |
E623795
|
entity |
| Predicate | usedAsBlendComponentWith |
P56866
|
FINISHED |
| Object | Malvasía Riojana |
—
|
NE NERFINISHED |
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: Malvasía Riojana | Statement: [Viura, usedAsBlendComponentWith, Malvasía Riojana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBlendComponentWith Context triple: [Viura, usedAsBlendComponentWith, Malvasía Riojana]
-
A.
hasBlendOf
Indicates that something is composed of or contains a mixture of multiple specified components or elements.
-
B.
usedInBlends
chosen
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
C.
isBlended
Indicates that one entity has been mixed or combined thoroughly with another (or others) to form a uniform whole.
-
D.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
E.
hasBlendOfOldAndNew
Indicates that something combines or integrates both traditional/older elements and modern/newer elements into a single whole.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:27 a.m.