Triple
T591811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probabilistic Encryption |
E17287
|
entity |
| Predicate | canAchieve |
P16015
|
FINISHED |
| Object | IND-CPA security |
—
|
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: IND-CPA security | Statement: [Probabilistic Encryption, canAchieve, IND-CPA security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAchieve Context triple: [Probabilistic Encryption, canAchieve, IND-CPA security]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
E.
achievementLevel
Indicates the degree or extent to which an entity has attained a particular goal, standard, or performance outcome.
- 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_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. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.