Triple

T30314472
Position Surface form Disambiguated ID Type / Status
Subject Google Domains E771023 entity
Predicate supportsTLDType P107023 FINISHED
Object generic top-level domains 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: generic top-level domains | Statement: [Google Domains, supportsTLDType, generic top-level domains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsTLDType
Context triple: [Google Domains, supportsTLDType, generic top-level domains]
  • A. TLDType
    Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
  • B. isOneOfOriginalGTLDs
    Indicates that the entity belongs to the set of domain names that were part of the original group of generic top-level domains (gTLDs) introduced in the early DNS system.
  • C. supportsDomainType chosen
    Indicates that one entity is capable of handling, operating with, or being applicable to a specified domain type.
  • D. supportsInternationalRegistrars
    Indicates that an entity is compatible with and provides services for registrars operating in multiple countries or international markets.
  • E. supportsType
    Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
  • 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_69f22488f224819081b0f3ec41ab975c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e2fac0819089b522db3260028c completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 7:51 p.m.