Triple

T994759
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.22 E21470 entity
Predicate regulatoryGoal P14666 FINISHED
Object non-interference with incumbent TV services 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: non-interference with incumbent TV services | Statement: [IEEE 802.22, regulatoryGoal, non-interference with incumbent TV services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryGoal
Context triple: [IEEE 802.22, regulatoryGoal, non-interference with incumbent TV services]
  • A. regulatoryType
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • B. regulatoryOutcome
    Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
  • C. strategicGoal
    Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
  • D. regulatoryDocument
    Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
  • E. hasPolicyGoal chosen
    Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4c75de88190bf7fec7a053f7a90 completed March 1, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69a4b2af071c819086c374a16307dfe0 completed March 1, 2026, 9:42 p.m.
Created at: March 1, 2026, 7:41 p.m.