Triple
T24909086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viura |
E623795
|
entity |
| Predicate | primaryRoleInRegion |
P134117
|
FINISHED |
| Object | primary white grape of Rioja |
—
|
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: primary white grape of Rioja | Statement: [Viura, primaryRoleInRegion, primary white grape of Rioja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInRegion Context triple: [Viura, primaryRoleInRegion, primary white grape of Rioja]
-
A.
principalRoleIn
chosen
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
B.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
C.
primaryRoleInHierarchy
Indicates that one entity holds the main or most important role or position within a defined hierarchy relative to another entity.
-
D.
primaryHubRegion
Indicates that a given region serves as the main or central hub location for an entity or system.
-
E.
professionalRegion
Indicates the geographic area or jurisdiction within which a professional activity, role, or responsibility is carried out.
- 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_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 5:27 a.m.