Triple
T29728459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baco Blanc |
E752251
|
entity |
| Predicate | legalStatusInArmagnac |
P83774
|
FINISHED |
| Object | authorized variety |
—
|
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: authorized variety | Statement: [Baco Blanc, legalStatusInArmagnac, authorized variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInArmagnac Context triple: [Baco Blanc, legalStatusInArmagnac, authorized variety]
-
A.
wineRegulationStatus
chosen
Indicates the regulatory classification or compliance status that applies to a given wine under relevant laws or standards.
-
B.
statusInFrance
Indicates the legal, social, or official standing or condition that an entity has within the jurisdiction of France.
-
C.
wineRegulationBody
Indicates that a regulatory organization has authority over the production, labeling, or distribution standards for a particular wine or wine-producing region.
-
D.
legalStatusInAlgeria
Indicates the legal status or standing that an entity holds under the laws and regulations of Algeria.
-
E.
appellationRules
Indicates the rules or conventions governing how something is named, titled, or designated in relation to another entity.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 28, 2026, 7:40 p.m.