Triple

T35656386
Position Surface form Disambiguated ID Type / Status
Subject Nizza DOCG E1030297 entity
Predicate legalRecognitionAsSeparateDOCG P200708 FINISHED
Object 2014 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: 2014 | Statement: [Nizza DOCG, legalRecognitionAsSeparateDOCG, 2014]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalRecognitionAsSeparateDOCG
Context triple: [Nizza DOCG, legalRecognitionAsSeparateDOCG, 2014]
  • A. legalRecognition
    Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
  • B. legalStatusRecognizedIn
    Indicates that an entity’s legal status is officially acknowledged or valid within a specified jurisdiction or legal system.
  • C. legalEmbodimentOf
    Indicates that one entity serves as the legally recognized form, vehicle, or representation through which another entity exists, acts, or holds rights and obligations in law.
  • D. legalDocumentRatified
    Indicates that a legal document has been formally approved and made officially valid by the appropriate authority or process.
  • E. recognizesDocument
    Indicates that one entity acknowledges the validity or authenticity of a document associated with another entity.
  • 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_69f76e0938088190a8f199631e97dec3 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ffa5f31c8881908c26e2aa52df6ece completed May 9, 2026, 9:24 p.m.
PD Predicate disambiguation batch_69ffa42aee408190ad1a5f285688b338 completed May 9, 2026, 9:16 p.m.
PDg Predicate description generation batch_69ffa5f236288190bdad97a41aca3cd8 completed May 9, 2026, 9:24 p.m.
Created at: May 3, 2026, 4:05 p.m.