Triple
T2735458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côte de Beaune-Villages AOC |
E60619
|
entity |
| Predicate | canBlendFrom |
P38059
|
FINISHED |
| Object | multiple villages in Côte de Beaune |
—
|
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: multiple villages in Côte de Beaune | Statement: [Côte de Beaune-Villages AOC, canBlendFrom, multiple villages in Côte de Beaune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBlendFrom Context triple: [Côte de Beaune-Villages AOC, canBlendFrom, multiple villages in Côte de Beaune]
-
A.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
B.
mixesWith
chosen
Indicates that one entity is combined or blended together with another entity to form a mixture.
-
C.
canBeObtainedFrom
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.