Triple
T31939831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copertino DOC |
E815492
|
entity |
| Predicate | alcoholMinimum |
P121997
|
FINISHED |
| Object | 12% ABV |
—
|
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: 12% ABV | Statement: [Copertino DOC, alcoholMinimum, 12% ABV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alcoholMinimum Context triple: [Copertino DOC, alcoholMinimum, 12% ABV]
-
A.
minimumAlcoholRegulated
Indicates that there is a legally or formally established minimum alcohol-related threshold (such as age, content, or quantity) that is subject to regulation.
-
B.
minimumAlcohol
chosen
Indicates that there is a specified minimum amount or concentration of alcohol required or present in the described context.
-
C.
higherMinimumAlcoholThan
Indicates that the minimum required or actual alcohol content of one entity is greater than that of another entity.
-
D.
drinksLegalAge
Indicates that an entity has reached the minimum legal age required to consume alcoholic beverages.
-
E.
alcoholRange
Indicates the range or interval of alcohol content associated with an entity (e.g., minimum and maximum alcohol level).
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2713c2881909e4d5e80aed67f09 |
completed | May 3, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:05 a.m.