Triple

T31933905
Position Surface form Disambiguated ID Type / Status
Subject Hárslevelű E815331 entity
Predicate roleInTokaj P57084 FINISHED
Object supporting variety to Furmint 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: supporting variety to Furmint | Statement: [Hárslevelű, roleInTokaj, supporting variety to Furmint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInTokaj
Context triple: [Hárslevelű, roleInTokaj, supporting variety to Furmint]
  • A. roleInCognac
    Indicates that an entity plays a specific role or function within the context of cognac (e.g., its production, classification, or related processes).
  • B. wineEconomyRole
    Indicates the role or function an entity has within the wine-related economy, such as production, distribution, trade, or regulation.
  • C. roleAtVine
    Indicates that an entity holds or held a specific role or position at the company Vine.
  • D. wineRegionRole
    Indicates the specific role or function that a wine-producing region has in relation to wine production, classification, or designation.
  • E. wineBlendRole chosen
    Indicates the specific role or function that a wine plays within a blend (e.g., primary component, supporting component, or minor addition).
  • 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_69f348f3035c81908558e2339955abb3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ffecdcbac4819093b725a7dbe0e61b completed May 10, 2026, 2:26 a.m.
PD Predicate disambiguation batch_69ffec3633288190adbbd84e277708dc completed May 10, 2026, 2:23 a.m.
Created at: May 1, 2026, 12:04 a.m.