Triple
T32498265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD4 |
E830583
|
entity |
| Predicate | roundFunctions |
P170950
|
FINISHED |
| Object | three distinct Boolean functions |
—
|
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: three distinct Boolean functions | Statement: [MD4, roundFunctions, three distinct Boolean functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundFunctions Context triple: [MD4, roundFunctions, three distinct Boolean functions]
-
A.
roundFunctionInput
Indicates that a given value is used as an input to a rounding function in a computation or process.
-
B.
roundFunctionType
Indicates that a function or operation is of a type that performs a rounding transformation on its input values.
-
C.
usesFinalPermutation
Indicates that an entity applies or relies on a final permutation step (typically a last reordering or transformation) within a process or algorithm.
-
D.
hasRoundFunction
chosen
Indicates that one entity possesses or is associated with a function that performs rounding operations.
-
E.
cryptFunction
Indicates a function or method that performs cryptographic processing, such as encrypting, decrypting, or otherwise transforming data using a cryptographic algorithm.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4409dc48190a9eac031b88571a1 |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.