Triple
T22499151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | fingerprintSHA1 |
P148464
|
FINISHED |
| Object | DAC9024F54D8F6DF94935FB1732638CA6AD77C13 |
—
|
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: DAC9024F54D8F6DF94935FB1732638CA6AD77C13 | Statement: [DST Root CA X3, fingerprintSHA1, DAC9024F54D8F6DF94935FB1732638CA6AD77C13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fingerprintSHA1 Context triple: [DST Root CA X3, fingerprintSHA1, DAC9024F54D8F6DF94935FB1732638CA6AD77C13]
-
A.
hasFingerprintSensor
Indicates that an entity is equipped with or includes a fingerprint recognition sensor.
-
B.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
C.
hasFingeringSystem
Indicates that an instrument or object is associated with a particular method or system for positioning fingers to produce notes or actions.
-
D.
hasFaceUnlock
Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
-
E.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
- 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.