Triple
T18683764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Côte AOC |
E456801
|
entity |
| Predicate | countryWineLaw |
P38943
|
FINISHED |
| Object | Swiss wine law |
—
|
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: Swiss wine law | Statement: [La Côte AOC, countryWineLaw, Swiss wine law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryWineLaw Context triple: [La Côte AOC, countryWineLaw, Swiss wine law]
-
A.
countryWineLawFramework
Indicates the legal and regulatory framework a country has established to govern the production, classification, distribution, and sale of wine.
-
B.
wineRegulationBody
Indicates that a regulatory organization has authority over the production, labeling, or distribution standards for a particular wine or wine-producing region.
-
C.
wineCountry
Indicates that a location is recognized as a region where wine is produced, typically known for its vineyards and wineries.
-
D.
wineLaw
chosen
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
E.
wineRegulationStatus
Indicates the regulatory classification or compliance status that applies to a given wine under relevant laws or standards.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2b819c8190b5f3d7a88607f6f5 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.