Triple
T15141964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .bw |
E361705
|
entity |
| Predicate | ICANNManagedZone |
P82708
|
FINISHED |
| Object | root zone |
—
|
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: root zone | Statement: [.bw, ICANNManagedZone, root zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICANNManagedZone Context triple: [.bw, ICANNManagedZone, root zone]
-
A.
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.
-
B.
ICANNRootZoneManagedBy
chosen
Indicates that the management and administrative control of a given DNS root zone is carried out by ICANN.
-
C.
ianaZoneFile
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
D.
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.
-
E.
ICANNDelegationStatus
Indicates the current status or outcome of ICANN’s delegation or redelegation decision for a particular top-level domain within the DNS.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c5c4248190b57234e3ccf2831b |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.