Triple
T31023039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empordà DO |
E790498
|
entity |
| Predicate | authorizedGrapes |
P37246
|
FINISHED |
| Object | native Catalan varieties |
—
|
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: native Catalan varieties | Statement: [Empordà DO, authorizedGrapes, native Catalan varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedGrapes Context triple: [Empordà DO, authorizedGrapes, native Catalan varieties]
-
A.
forbidsGrape
Indicates that one entity prohibits or does not allow the use, presence, or consumption of grapes in relation to another entity.
-
B.
grapeVarietyAllowed
chosen
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
-
C.
hasRegulatedGrapes
Indicates that certain grapes are subject to specific rules, standards, or controls imposed by an authority or regulation.
-
D.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
E.
authorizedAccessoryRedGrape
Indicates that an accessory or related item is officially permitted or approved in the context of red grapes.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 8:58 p.m.