Triple
T32023730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borderies (Cognac cru) |
E817761
|
entity |
| Predicate | eauxDeVieBody |
P20482
|
FINISHED |
| Object | medium-bodied |
—
|
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: medium-bodied | Statement: [Borderies (Cognac cru), eauxDeVieBody, medium-bodied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eauxDeVieBody Context triple: [Borderies (Cognac cru), eauxDeVieBody, medium-bodied]
-
A.
eauxDeVieStyle
Indicates a relationship where something is characterized as being in the style or manner of eaux-de-vie (fruit brandy), typically referring to how it is produced, flavored, or presented.
-
B.
wineComponent
Indicates that one entity is a constituent ingredient or part of a wine represented by the other entity.
-
C.
wineDenomination
Indicates that a wine is classified under a specific official denomination or appellation.
-
D.
wineStructure
chosen
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
E.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
- 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_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:17 a.m.