Triple
T31202116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco di Tufo wine |
E795502
|
entity |
| Predicate | minimumGrecoContent |
P173434
|
FINISHED |
| Object | 85% |
—
|
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: 85% | Statement: [Greco di Tufo wine, minimumGrecoContent, 85%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumGrecoContent Context triple: [Greco di Tufo wine, minimumGrecoContent, 85%]
-
A.
minimumFianoContent
Indicates that there is a specified minimum required amount or proportion of Fiano content in a given item or mixture.
-
B.
minimumVernacciaContent
Indicates the required minimum amount or proportion of Vernaccia content that must be present in a given product or mixture.
-
C.
minimumPrimitivoContent
Indicates that there is a specified minimum amount or level of primitive content required in the relationship between the involved entities.
-
D.
providesToGreeks
Indicates that one entity supplies or makes something available to Greek individuals or groups.
-
E.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 29, 2026, 9:09 p.m.