Triple
T9403379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-root |
E226528
|
entity |
| Predicate | improvesProperty |
P68214
|
FINISHED |
| Object | DNS resilience |
—
|
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: DNS resilience | Statement: [I-root, improvesProperty, DNS resilience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvesProperty Context triple: [I-root, improvesProperty, DNS resilience]
-
A.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
improvesAccessToward
Indicates that one entity enhances or facilitates the ability of another entity to reach, use, or benefit from a resource, service, or opportunity.
-
C.
seeksToImprove
Indicates an intentional effort by one entity to make another entity or condition better than its current state.
-
D.
changesProperty
chosen
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
E.
claimsToImprove
Indicates that one entity asserts or promises that it will enhance, benefit, or make another entity better in some way.
- 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.