Triple

T287289
Position Surface form Disambiguated ID Type / Status
Subject Domain Name System root zone E5910 entity
Predicate hasChangeControl P9249 FINISHED
Object IANA root zone management process 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: IANA root zone management process | Statement: [Domain Name System root zone, hasChangeControl, IANA root zone management process]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasChangeControl
Context triple: [Domain Name System root zone, hasChangeControl, IANA root zone management process]
  • A. hasLegalChange
    Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
  • B. hasControlTower
    Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
  • C. hasEntranceControl
    Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
  • D. hasCheckAndBalanceWith
    Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
  • E. hasCheckAndBalanceFunction
    Indicates that one entity performs a checking or limiting role on another entity’s powers, providing oversight and balance within a system.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a25e2ddaa88190b08c40b5823f30a0 completed Feb. 28, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69a25b7c1448819082064f474633acd5 completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25d3463648190ac716d7475378536 completed Feb. 28, 2026, 3:12 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.