Triple
T830254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malbec |
E17947
|
entity |
| Predicate | commonUse |
P11801
|
FINISHED |
| Object | single-varietal wines |
—
|
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: single-varietal wines | Statement: [Malbec, commonUse, single-varietal wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonUse Context triple: [Malbec, commonUse, single-varietal wines]
-
A.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
B.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
C.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb384988190949d2df65662f76d |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.