Triple
T9932132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed448 |
E192670
|
entity |
| Predicate | curveFieldSize |
P7759
|
FINISHED |
| Object | 448-bit prime field |
—
|
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: 448-bit prime field | Statement: [Ed448, curveFieldSize, 448-bit prime field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curveFieldSize Context triple: [Ed448, curveFieldSize, 448-bit prime field]
-
A.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
curveRadius
Indicates the radius of curvature associated with an object or path, describing how sharply it bends at a given point.
-
C.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
D.
typicalFieldStrength
Indicates the usual or characteristic magnitude of a field (such as electric, magnetic, or other physical field) associated with an entity or situation.
-
E.
fieldDesign
Indicates a relationship where an entity is responsible for planning, arranging, or specifying the layout and structure of a particular field or area.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.