Triple
T29213670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sousa |
E740606
|
entity |
| Predicate | notableWineAttribute |
P16142
|
FINISHED |
| Object | refreshing character |
—
|
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: refreshing character | Statement: [Sousa, notableWineAttribute, refreshing character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWineAttribute Context triple: [Sousa, notableWineAttribute, refreshing character]
-
A.
wineCharacteristic
chosen
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
B.
oenologicalProperty
Indicates a relationship where a characteristic or attribute is specifically related to wine or the science of winemaking.
-
C.
notableWine
Indicates that a wine is recognized as significant, distinguished, or noteworthy in some context (such as quality, reputation, or historical importance).
-
D.
appellationType
Indicates the specific kind or category of name or designation applied to an entity.
-
E.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
Created at: April 28, 2026, 12:12 p.m.