Triple

T6997863
Position Surface form Disambiguated ID Type / Status
Subject Protected Geographical Indication E162262 entity
Predicate protectionScope P15826 FINISHED
Object protection against misuse of registered names 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: protection against misuse of registered names | Statement: [Protected Geographical Indication, protectionScope, protection against misuse of registered names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protectionScope
Context triple: [Protected Geographical Indication, protectionScope, protection against misuse of registered names]
  • A. protectionLevel
    Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
  • B. protectionCategory
    Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
  • C. protectionType chosen
    Indicates the kind or method of protection that is applied to or associated with an entity.
  • D. isProtectedFor
    Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
  • E. accessScope
    Indicates the extent or boundaries of access that one entity has to another entity or resource.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbeef57881909245c8a5374a8111 completed March 27, 2026, 7:35 p.m.
PD Predicate disambiguation batch_69c6d7c67c94819084fdcf0398606027 completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:33 p.m.