Triple

T5876732
Position Surface form Disambiguated ID Type / Status
Subject Geneva wine region E130642 entity
Predicate usesTrainingSystem P11879 FINISHED
Object Guyot pruning 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: Guyot pruning | Statement: [Geneva wine region, usesTrainingSystem, Guyot pruning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTrainingSystem
Context triple: [Geneva wine region, usesTrainingSystem, Guyot pruning]
  • A. trainingSystem chosen
    Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
  • B. trainingUse
    Indicates that something is used for training purposes, such as preparing, educating, or improving the skills or performance of an entity.
  • C. hasTrainingComplex
    Indicates that an entity possesses or is associated with a dedicated facility or complex used for training activities.
  • D. hasTrainingFor
    Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
  • E. providesTrainingFor
    Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of 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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0432fea5881909f5c291dd8db6105 completed March 22, 2026, 7:29 p.m.
PD Predicate disambiguation batch_69c033499ca08190bd26cee5b03f6306 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 3:57 p.m.