Triple
T17677310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1.1.1.1 DNS resolver |
E440671
|
entity |
| Predicate | dataRetentionLimit |
P93788
|
FINISHED |
| Object | 24 hours for non-essential logs |
—
|
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: 24 hours for non-essential logs | Statement: [1.1.1.1 DNS resolver, dataRetentionLimit, 24 hours for non-essential logs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRetentionLimit Context triple: [1.1.1.1 DNS resolver, dataRetentionLimit, 24 hours for non-essential logs]
-
A.
dataRetentionPeriod
chosen
Indicates the length of time data is stored or kept before it is deleted, archived, or otherwise disposed of.
-
B.
storageLimitPolicy
Indicates the rules or constraints that govern how much and how long data or items may be stored.
-
C.
retentionMethod
Indicates the method or strategy used to retain or keep something (such as data, customers, or resources) over time.
-
D.
headRetention
Indicates that an entity maintains or preserves its leadership, primary position, or top status over time or through a given event or process.
-
E.
leafRetention
Indicates whether an entity retains its leaves (e.g., remains evergreen) or sheds them seasonally.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.