Triple

T22499152
Position Surface form Disambiguated ID Type / Status
Subject DST Root CA X3 E556221 entity
Predicate fingerprintSHA256 P148465 FINISHED
Object 0687260331A72403D909F105E69BCF0D32E1BD2493FFC6D9206D11B6C61F81C5 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: 0687260331A72403D909F105E69BCF0D32E1BD2493FFC6D9206D11B6C61F81C5 | Statement: [DST Root CA X3, fingerprintSHA256, 0687260331A72403D909F105E69BCF0D32E1BD2493FFC6D9206D11B6C61F81C5]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fingerprintSHA256
Context triple: [DST Root CA X3, fingerprintSHA256, 0687260331A72403D909F105E69BCF0D32E1BD2493FFC6D9206D11B6C61F81C5]
  • A. hasFingerprintSensor
    Indicates that an entity is equipped with or includes a fingerprint recognition sensor.
  • B. hasFaceUnlock
    Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
  • C. dataDiFirma
    Indicates the date on which a document or agreement was signed.
  • D. signatureEquipment
    Indicates that the object is a distinctive or characteristic piece of equipment closely associated with a particular entity.
  • E. signatureFeature
    Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
  • 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.