Triple
T9403391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-root |
E226528
|
entity |
| Predicate | hasDNSRole |
P14843
|
FINISHED |
| Object | top-level of DNS hierarchy |
—
|
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: top-level of DNS hierarchy | Statement: [I-root, hasDNSRole, top-level of DNS hierarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDNSRole Context triple: [I-root, hasDNSRole, top-level of DNS hierarchy]
-
A.
hasDNSLabel
Indicates that an entity is associated with, or identified by, a specific DNS label (a name component within the Domain Name System).
-
B.
DNS
chosen
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.
-
C.
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.
-
D.
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.
-
E.
hasCatchallRole
Indicates that an entity holds a broad, non-specific role intended to cover responsibilities not captured by more specialized roles.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.