Triple
T2113817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pageant |
E42561
|
entity |
| Predicate | supportsKeyType |
P9247
|
FINISHED |
| Object | ECDSA |
E195587
|
NE 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: ECDSA | Statement: [Pageant, supportsKeyType, ECDSA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECDSA Context triple: [Pageant, supportsKeyType, ECDSA]
-
A.
Elliptic Curve Digital Signature Algorithm
chosen
Elliptic Curve Digital Signature Algorithm is a public-key cryptographic method that uses elliptic curve mathematics to create compact, secure digital signatures for authentication and data integrity.
-
B.
Ed25519
Ed25519 is a high-speed, high-security elliptic-curve digital signature scheme widely used in modern cryptographic protocols and software.
-
C.
ECC
ECC is a public-key cryptography approach that uses the mathematics of elliptic curves to provide strong security with relatively small key sizes.
-
D.
ECC
ECC is the National Rail station code for Eccles railway station in Greater Manchester, England.
-
E.
Ed448
Ed448 is a modern high-security elliptic-curve digital signature algorithm designed for strong cryptographic assurance and efficient performance.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae30748a7c81908ab3e08b7aa9900a |
completed | March 9, 2026, 2:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.