Triple
T591797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probabilistic Encryption |
E17287
|
entity |
| Predicate | canBeBuiltFrom |
P8649
|
FINISHED |
| Object | trapdoor permutations |
—
|
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: trapdoor permutations | Statement: [Probabilistic Encryption, canBeBuiltFrom, trapdoor permutations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBuiltFrom Context triple: [Probabilistic Encryption, canBeBuiltFrom, trapdoor permutations]
-
A.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
B.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
canBeImplementedWith
chosen
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbaf53081908eed240bed09f63b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.