Triple
T6653807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbera d’Asti |
E150889
|
entity |
| Predicate | EUClassification |
P44958
|
FINISHED |
| Object | PDO |
—
|
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: PDO | Statement: [Barbera d’Asti, EUClassification, PDO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EUClassification Context triple: [Barbera d’Asti, EUClassification, PDO]
-
A.
classificationByEuropeanUnion
chosen
Indicates the categorization or regulatory status assigned to an entity according to European Union classification systems or standards.
-
B.
classificationByUK
Indicates a relationship where an entity is assigned a category, status, or type according to a United Kingdom–specific classification system.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
governingClassification
Indicates the classification system or category framework that determines how an entity is organized, labeled, or regulated.
-
E.
isoClassificationStatus
Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.