Triple
T29840509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madiran |
E757779
|
entity |
| Predicate | localWineClassification |
P157224
|
FINISHED |
| Object | Appellation d’Origine Contrôlée |
—
|
NE NERFINISHED |
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: Appellation d’Origine Contrôlée | Statement: [Madiran, localWineClassification, Appellation d’Origine Contrôlée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localWineClassification Context triple: [Madiran, localWineClassification, Appellation d’Origine Contrôlée]
-
A.
wineClassificationSystem
Indicates a system or scheme used to categorize and organize wines based on defined criteria such as origin, style, or quality.
-
B.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
C.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
D.
wineDenomination
chosen
Indicates that a wine is classified under a specific official denomination or appellation.
-
E.
wineStyleOrigin
Indicates that a particular wine style originated in or is traditionally associated with a specific geographic region or place.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 5:39 p.m.