Triple
T32023640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Champagne (Cognac cru) |
E817759
|
entity |
| Predicate | typicalAromasAfterLongAging |
P152625
|
FINISHED |
| Object | rancio |
—
|
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: rancio | Statement: [Grande Champagne (Cognac cru), typicalAromasAfterLongAging, rancio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAromasAfterLongAging Context triple: [Grande Champagne (Cognac cru), typicalAromasAfterLongAging, rancio]
-
A.
characteristicAroma
chosen
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
B.
wineAgeingPotential
Indicates the capacity or suitability of a wine to improve in quality or maintain desirable characteristics over time with proper aging.
-
C.
wineAgeingPreference
Indicates a preference for how long wine should be aged before consumption or use.
-
D.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
E.
wineAgingVessel
Indicates the type of container or vessel in which a wine is aged.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.