Triple
T5591568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côtes du Rhône |
E146888
|
entity |
| Predicate | wineLawSystem |
P38943
|
FINISHED |
| Object | French AOC system |
—
|
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: French AOC system | Statement: [Côtes du Rhône, wineLawSystem, French AOC system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineLawSystem Context triple: [Côtes du Rhône, wineLawSystem, French AOC system]
-
A.
wineLaw
chosen
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution 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.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
D.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
E.
wineExport
Indicates a relationship where one entity exports wine to another entity or destination.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020a3365c8190bd223226c0a6969f |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.