Triple

T16410601
Position Surface form Disambiguated ID Type / Status
Subject Bordeaux Supérieur AOC E398551 entity
Predicate requiresLowerMaximumYields P123321 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: [Bordeaux Supérieur AOC, requiresLowerMaximumYields, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresLowerMaximumYields
Context triple: [Bordeaux Supérieur AOC, requiresLowerMaximumYields, yes]
  • A. hasYield
    Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
  • B. yieldLevel
    Indicates the degree or amount of output or production resulting from a process, resource, or entity.
  • C. relativeYieldComparedToW76
    Indicates the yield of something expressed in comparison to the yield of the reference item W76, typically as a ratio or relative measure.
  • D. hasHigherListingRequirementsThan
    Indicates that one entity is subject to stricter or more demanding listing requirements than another entity.
  • E. hasMaximumEfficiencyAt
    Indicates that an entity reaches or exhibits its highest possible efficiency under a specified condition, context, or parameter value.
  • F. None of above. chosen

Provenance (4 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328731a408190b38dcab0b7bb65ff completed April 18, 2026, 6:45 a.m.
PD Predicate disambiguation batch_69e226fe1dd08190865c181721f8c348 completed April 17, 2026, 12:26 p.m.
PDg Predicate description generation batch_69e24555bb6c8190977cf5c5f9149056 completed April 17, 2026, 2:36 p.m.
Created at: April 10, 2026, 5:09 a.m.