Triple
T13281216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizza Monferrato |
E316323
|
entity |
| Predicate | wineZoneStatus |
P109304
|
FINISHED |
| Object | core area for Barbera d’Asti production |
—
|
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: core area for Barbera d’Asti production | Statement: [Nizza Monferrato, wineZoneStatus, core area for Barbera d’Asti production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineZoneStatus Context triple: [Nizza Monferrato, wineZoneStatus, core area for Barbera d’Asti production]
-
A.
wineRegionStatus
Indicates the official classification or recognition status assigned to a wine-producing region.
-
B.
wineRegulationStatus
Indicates the regulatory classification or compliance status that applies to a given wine under relevant laws or standards.
-
C.
viniferaStatus
Indicates the classification or condition of an entity with respect to being Vitis vinifera (e.g., whether and how it is identified or treated as vinifera).
-
D.
wineRegionGatewayTo
Indicates that one wine region serves as an entry point or primary access route to another wine region.
-
E.
hasWineDenomination
Indicates that a wine is classified under a specific official denomination or appellation.
- F. None of above. chosen
Provenance (4 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:27 p.m.