Triple
T9623570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château Haut-Bailly |
E232402
|
entity |
| Predicate | typicalBlendSecondaryVariety |
P2076
|
FINISHED |
| Object | Merlot |
—
|
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 | Statement: [Château Haut-Bailly, typicalBlendSecondaryVariety, Merlot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBlendSecondaryVariety Context triple: [Château Haut-Bailly, typicalBlendSecondaryVariety, Merlot]
-
A.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
B.
secondaryColour
Indicates that one entity serves as a secondary or accent color in relation to another entity’s primary color.
-
C.
typicalBlendPartner
chosen
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
-
D.
secondaryBranchColor
Indicates the color assigned to a secondary or subordinate branch in relation to a primary branch.
-
E.
primaryWhiteVariety
Indicates that one entity is the primary white (light-skinned or white-colored) variety or form of another entity.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad650a4819096258665bc3f410b |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.