Triple
T26408702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noekeon |
E663898
|
entity |
| Predicate | roundTransformation |
P162804
|
FINISHED |
| Object | Sigma round constant addition |
—
|
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: Sigma round constant addition | Statement: [Noekeon, roundTransformation, Sigma round constant addition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundTransformation Context triple: [Noekeon, roundTransformation, Sigma round constant addition]
-
A.
roundTransformation
chosen
Indicates a transformation process that occurs in discrete rounds or stages, where each round converts an input state into a new output state.
-
B.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
C.
rounded
Indicates that one entity has been made or become rounder or more curved in shape, often by smoothing or adjusting its edges or values.
-
D.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
E.
roundFunctionInput
Indicates that a given value is used as an input to a rounding function in a computation or process.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 11:36 p.m.