Triple
T26409168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHASH |
E663911
|
entity |
| Predicate | combinationOperation |
P12126
|
FINISHED |
| Object | XOR of polynomial multiplication results |
—
|
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: XOR of polynomial multiplication results | Statement: [GHASH, combinationOperation, XOR of polynomial multiplication results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinationOperation Context triple: [GHASH, combinationOperation, XOR of polynomial multiplication results]
-
A.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
junctionOf
Indicates that one or more entities meet or intersect at a common point, forming a junction between them.
-
D.
operationOf
chosen
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
- 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_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:37 p.m.