Triple

T338702
Position Surface form Disambiguated ID Type / Status
Subject X.509 certificate E6784 entity
Predicate supportsRevocationVia P203 FINISHED
Object certificate revocation list 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: certificate revocation list | Statement: [X.509 certificate, supportsRevocationVia, certificate revocation list]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRevocationVia
Context triple: [X.509 certificate, supportsRevocationVia, certificate revocation list]
  • A. revocationReason
    Indicates the reason or cause for which a previously granted status, permission, or credential has been revoked.
  • B. supportsClaim
    Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
  • C. supportsPolicy
    Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
  • D. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • E. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eae3a27c81909fc7deb600125fb1 completed Feb. 28, 2026, 1:17 p.m.
PD Predicate disambiguation batch_69a2e95067e88190a914a1c1d0283dfc completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.