Triple
T6674274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukuzani |
E151809
|
entity |
| Predicate | mainGrapeOrigin |
P975
|
FINISHED |
| Object | indigenous Georgian variety |
—
|
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: indigenous Georgian variety | Statement: [Mukuzani, mainGrapeOrigin, indigenous Georgian variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGrapeOrigin Context triple: [Mukuzani, mainGrapeOrigin, indigenous Georgian variety]
-
A.
grapeSource
Indicates that one entity is the origin or provider of grapes used by another entity.
-
B.
primaryGrapeVariety
chosen
Indicates that one entity is the main or predominant grape variety used in producing the other entity (typically a wine or wine-based product).
-
C.
primaryGrapeUse
Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
-
D.
traditionalGrapeVariety
Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
-
E.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c0aa8c5c8190a302b261f11b70cb |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0b6d00819086205b8ce30dd045 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.