Triple

T12347186
Position Surface form Disambiguated ID Type / Status
Subject Crémant de Loire E294384 entity
Predicate legalYieldControlled P104594 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: [Crémant de Loire, legalYieldControlled, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalYieldControlled
Context triple: [Crémant de Loire, legalYieldControlled, yes]
  • A. legalConstraint
    Indicates that one entity imposes or is subject to a rule, restriction, or requirement defined by a legal or regulatory framework in relation to another entity or action.
  • B. legalAuthorityIn
    Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
  • C. legalLicenseIn
    Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
  • D. legalAct
    Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
  • E. legalHolding
    Indicates that an entity possesses or controls something (such as property, assets, or rights) in a manner recognized and defined by law.
  • 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_69d6ab6ccbec8190b09e2d357aa80064 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f7ba17481908b03af7316b28d9b completed April 10, 2026, 6:20 p.m.
PD Predicate disambiguation batch_69d93ecb5efc819086a3530282278bb1 completed April 10, 2026, 6:17 p.m.
PDg Predicate description generation batch_69d93f607a88819089e89fd263ae9937 completed April 10, 2026, 6:20 p.m.
Created at: April 8, 2026, 9:53 p.m.