Triple
T16477314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friuli Doc festival |
E400222
|
entity |
| Predicate | typeOfWineFestival |
P122926
|
FINISHED |
| Object | regional wine festival |
—
|
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: regional wine festival | Statement: [Friuli Doc festival, typeOfWineFestival, regional wine festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWineFestival Context triple: [Friuli Doc festival, typeOfWineFestival, regional wine festival]
-
A.
wineVariety
Indicates the specific type or variety of wine associated with an entity.
-
B.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
C.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
D.
regulatesWineType
Indicates that one entity has authority or influence over the rules, standards, or conditions governing a particular type of wine.
-
E.
wineTypeAllowed
Indicates that a particular type of wine is permitted or acceptable in a given context or for a given purpose.
- F. None of above. chosen
Provenance (4 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e0013ac8190b607d5f47d17c501 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.