Triple
T34852815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garganega |
E1004643
|
entity |
| Predicate | typicalBlendingPartners |
P2076
|
FINISHED |
| Object | Trebbiano di Soave |
E573128
|
NE 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: Trebbiano di Soave | Statement: [Garganega, typicalBlendingPartners, Trebbiano di Soave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBlendingPartners Context triple: [Garganega, typicalBlendingPartners, Trebbiano di Soave]
-
A.
typicalBlendPartner
chosen
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
-
B.
hasBlendOf
Indicates that something is composed of or contains a mixture of multiple specified components or elements.
-
C.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
D.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
E.
isBlended
Indicates that one entity has been mixed or combined thoroughly with another (or others) to form a uniform whole.
- F. None of above.
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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8a390a08190895bb1910dfaf5a5 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.