Triple
T2998262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château Pétrus |
E81122
|
entity |
| Predicate | grapeComposition |
P11949
|
FINISHED |
| Object | Merlot-dominant blend |
—
|
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: Merlot-dominant blend | Statement: [Château Pétrus, grapeComposition, Merlot-dominant blend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeComposition Context triple: [Château Pétrus, grapeComposition, Merlot-dominant blend]
-
A.
grapeColorProduced
Indicates the color that is produced by or characteristic of a given grape.
-
B.
grapeVarietyAllowed
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
-
C.
primaryGrapeVariety
Indicates that one entity is the main or predominant grape variety used in producing the other entity (typically a wine or wine-based product).
-
D.
usesGrapeType
chosen
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
E.
secondaryGrape
Indicates that one grape variety serves as a secondary or supporting component in a wine blend relative to the primary grape.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.