Triple
T1712049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSSEC |
E37203
|
entity |
| Predicate | rootZoneSigned |
P32231
|
FINISHED |
| Object | 2010-07-15 |
—
|
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: 2010-07-15 | Statement: [DNSSEC, rootZoneSigned, 2010-07-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rootZoneSigned Context triple: [DNSSEC, rootZoneSigned, 2010-07-15]
-
A.
ianaZoneFile
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
B.
DNSSECSupported
Indicates that a domain or DNS service supports and correctly implements DNSSEC security extensions for authenticating DNS data.
-
C.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
-
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.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab752034348190a1cc20955ed24f6f |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:30 p.m.