Triple
T29944274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sémillon–Sauvignon Blanc–Muscadelle |
E760588
|
entity |
| Predicate | isClassicBlendOfRegion |
P115331
|
FINISHED |
| Object | Bordeaux white wines |
—
|
NE NERFINISHED |
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: Bordeaux white wines | Statement: [Sémillon–Sauvignon Blanc–Muscadelle, isClassicBlendOfRegion, Bordeaux white wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassicBlendOfRegion Context triple: [Sémillon–Sauvignon Blanc–Muscadelle, isClassicBlendOfRegion, Bordeaux white wines]
-
A.
isClassicOfArea
chosen
Indicates that something is recognized as a classic or exemplary work within a particular area, field, or domain.
-
B.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
C.
isTraditionalInCountry
Indicates that something is customary, long-established, or commonly practiced within a particular country.
-
D.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or entity.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780a76b0819091e8781ee21191ac |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:23 p.m.