Triple

T31763548
Position Surface form Disambiguated ID Type / Status
Subject Commune of Mercurey E810743 entity
Predicate hasWineRegulationBody P41067 FINISHED
Object INAO (France) NE NERFINISHED

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: INAO (France) | Statement: [Commune of Mercurey, hasWineRegulationBody, INAO (France)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWineRegulationBody
Context triple: [Commune of Mercurey, hasWineRegulationBody, INAO (France)]
  • A. wineRegulationBody chosen
    Indicates that a regulatory organization has authority over the production, labeling, or distribution standards for a particular wine or wine-producing region.
  • B. countryWineLawFramework
    Indicates the legal and regulatory framework a country has established to govern the production, classification, distribution, and sale of wine.
  • C. hasWineDenomination
    Indicates that a wine is classified under a specific official denomination or appellation.
  • D. wineRegulationStatus
    Indicates the regulatory classification or compliance status that applies to a given wine under relevant laws or standards.
  • E. regulatesWineType
    Indicates that one entity has authority or influence over the rules, standards, or conditions governing a particular type of wine.
  • 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_69f348e463e08190b902d4819195e1f0 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f71996e1a48190ac59a1d66d7c44e8 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71820c6c88190ab38b4fa626d22cc completed May 3, 2026, 9:40 a.m.
Created at: April 30, 2026, 11:31 p.m.