Triple
T4970922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscat de Frontignan AOC |
E111645
|
entity |
| Predicate | grapeType |
P37246
|
FINISHED |
| Object | Muscat grape |
—
|
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: Muscat grape | Statement: [Muscat de Frontignan AOC, grapeType, Muscat grape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeType Context triple: [Muscat de Frontignan AOC, grapeType, Muscat grape]
-
A.
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).
-
B.
grapeVarietyAllowed
chosen
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.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
D.
traditionalGrapeVariety
Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
-
E.
grapeSource
Indicates that one entity is the origin or provider of grapes used by 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.