Triple
T287254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSA |
E5909
|
entity |
| Predicate | publicKeyComponent |
P5688
|
FINISHED |
| Object | modulus n |
—
|
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: modulus n | Statement: [RSA, publicKeyComponent, modulus n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicKeyComponent Context triple: [RSA, publicKeyComponent, modulus n]
-
A.
keyComponent
chosen
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
B.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for another entity.
-
C.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
D.
keyManagementType
Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
-
E.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2ddaa88190b08c40b5823f30a0 |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.