Triple
T22499150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | isExpired |
P148463
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DST Root CA X3, isExpired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpired Context triple: [DST Root CA X3, isExpired, true]
-
A.
canExpire
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
B.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
C.
doesNotExpire
Indicates that the entity remains valid indefinitely and is not subject to an expiration or end date.
-
D.
isIssued
Indicates that an authoritative source formally provides, distributes, or makes something (such as a document, order, or item) officially available to a recipient.
-
E.
consequenceOfExpiry
Indicates that something occurs as a direct result of an expiry event or the state of having expired.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb3deb88190874230ae06a352d6 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.