Triple

T4490330
Position Surface form Disambiguated ID Type / Status
Subject Tsitska E107355 entity
Predicate usedInTraditionalWinemaking P28269 FINISHED
Object yes 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: yes | Statement: [Tsitska, usedInTraditionalWinemaking, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInTraditionalWinemaking
Context triple: [Tsitska, usedInTraditionalWinemaking, yes]
  • A. traditionalVinification
    Indicates that a wine is produced using traditional or historically established winemaking methods rather than modern or industrial techniques.
  • B. oenologicalSignificance
    Indicates the relationship in which something holds importance, relevance, or notable impact within the context of wine or winemaking.
  • C. traditionalGrapeVariety chosen
    Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
  • D. primaryGrapeUse
    Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
  • E. vinification
    Indicates the process by which grapes (or other fruits) are transformed into wine through fermentation and related winemaking steps.
  • 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_69bd43f84f788190a1383579c4a595be completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd556d29f08190bab1e872dd7e819f completed March 20, 2026, 2:10 p.m.
PD Predicate disambiguation batch_69bd5213e3d0819094b026989e686f01 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 12:59 p.m.