Triple
T30091699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morellino di Scansano |
E764750
|
entity |
| Predicate | allowedWineTypes |
P112913
|
FINISHED |
| Object | rosso |
—
|
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: rosso | Statement: [Morellino di Scansano, allowedWineTypes, rosso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedWineTypes Context triple: [Morellino di Scansano, allowedWineTypes, rosso]
-
A.
wineTypeAllowed
chosen
Indicates that a particular type of wine is permitted or acceptable in a given context or for a given purpose.
-
B.
regulatesWineType
Indicates that one entity has authority or influence over the rules, standards, or conditions governing a particular type of wine.
-
C.
grapeVarietyAllowed
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
-
D.
sparklingWineAllowed
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
-
E.
usesWineType
Indicates that one entity makes use of, incorporates, or is associated with a particular type or category of wine.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 7:06 p.m.