Triple
T26408274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBC-MAC |
E663889
|
entity |
| Predicate | canShareKeyWith |
P160513
|
FINISHED |
| Object | encryption only with careful design |
—
|
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: encryption only with careful design | Statement: [CBC-MAC, canShareKeyWith, encryption only with careful design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canShareKeyWith Context triple: [CBC-MAC, canShareKeyWith, encryption only with careful design]
-
A.
canBeSharedTo
Indicates that something is capable of being shared or distributed to a particular recipient or destination.
-
B.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
C.
allowsShares
Indicates that one entity grants another entity permission to share or distribute something.
-
D.
sharesControlWith
Indicates that control, authority, or decision-making power over something is jointly held or exercised between the related entities.
-
E.
sharesUSRightsWith
Indicates that one entity holds and grants to another entity shared rights or interests specifically related to the United States.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:36 p.m.