Triple
T14406353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durif |
E357205
|
entity |
| Predicate | typicalUseInBlends |
P56866
|
FINISHED |
| Object | to add color |
—
|
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: to add color | Statement: [Durif, typicalUseInBlends, to add color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseInBlends Context triple: [Durif, typicalUseInBlends, to add color]
-
A.
usedInBlends
chosen
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
B.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
C.
typicalBlendPartner
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908804048190a4fe58afc2e0a5b6 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.