Triple

T4537104
Position Surface form Disambiguated ID Type / Status
Subject .me E107432 entity
Predicate ICANNDelegation P12950 FINISHED
Object 2007 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: 2007 | Statement: [.me, ICANNDelegation, 2007]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ICANNDelegation
Context triple: [.me, ICANNDelegation, 2007]
  • A. ICANNApproved
    Indicates that an entity (such as a domain, registrar, or policy) has been formally reviewed and granted approval by ICANN, the Internet Corporation for Assigned Names and Numbers.
  • B. DNSZone
    Indicates a relationship where a set of DNS records is grouped and managed together under a specific domain namespace as a single administrative unit.
  • C. ianaZoneFile chosen
    Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
  • D. DNS
    Indicates a relationship where one entity serves as or is associated with a Domain Name System (DNS) configuration or service for another entity, enabling the translation of domain names to network addresses.
  • E. IDNSupport
    Indicates that an entity provides or enables support for Internationalized Domain Names (IDNs), such as registering, resolving, or handling domain names with non-ASCII characters.
  • 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_69bd43f922788190b7edfa294e39b178 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57b78b8481909d79131723d4be22 completed March 20, 2026, 2:20 p.m.
PD Predicate disambiguation batch_69bd521edd00819099dfccaa65dddd61 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:04 p.m.