Triple
T4115694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costières de Nîmes AOC |
E90284
|
entity |
| Predicate | wineRegulationType |
P38943
|
FINISHED |
| Object | AOC regulations |
—
|
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: AOC regulations | Statement: [Costières de Nîmes AOC, wineRegulationType, AOC regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineRegulationType Context triple: [Costières de Nîmes AOC, wineRegulationType, AOC regulations]
-
A.
wineRegulationBody
Indicates that a regulatory organization has authority over the production, labeling, or distribution standards for a particular wine or wine-producing region.
-
B.
wineLaw
chosen
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
C.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
D.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
E.
hasWineDenomination
Indicates that a wine is classified under a specific official denomination or appellation.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.