Triple
T26409193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCM |
E663912
|
entity |
| Predicate | MACComputedOver |
P49064
|
FINISHED |
| Object | ciphertext and associated data |
—
|
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: ciphertext and associated data | Statement: [CCM, MACComputedOver, ciphertext and associated data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MACComputedOver Context triple: [CCM, MACComputedOver, ciphertext and associated data]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
isUsedToCompute
chosen
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
calculated
Indicates that one entity has determined or computed a value, result, or outcome based on information from another entity.
-
D.
tagComputation
Indicates a relationship where a specific computation is associated with, or labeled by, a particular tag for identification or categorization purposes.
-
E.
targetComputation
Indicates a relationship where one computation is designated or identified as the specific goal, focus, or intended result among possible computations.
- 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_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. |
Created at: April 26, 2026, 11:37 p.m.