Triple
T22499153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | keyIdentifier |
P148466
|
FINISHED |
| Object | C4A7B1A47B2C71F0 |
—
|
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: C4A7B1A47B2C71F0 | Statement: [DST Root CA X3, keyIdentifier, C4A7B1A47B2C71F0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyIdentifier Context triple: [DST Root CA X3, keyIdentifier, C4A7B1A47B2C71F0]
-
A.
keyIssueForIdentity
Indicates that something is a central or defining factor in shaping an entity’s identity.
-
B.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
C.
keyInterface
Indicates that one entity functions as the primary or main interface through which another entity is accessed or interacted with.
-
D.
keyIntermediate
Indicates that something serves as an essential transitional or intermediary step, component, or stage within a larger process or relationship.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of 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.