Triple
T32516992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curve448 |
E831085
|
entity |
| Predicate | curveForm |
P91205
|
FINISHED |
| Object | Montgomery curve |
—
|
NE NERFINISHED |
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: Montgomery curve | Statement: [Curve448, curveForm, Montgomery curve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curveForm Context triple: [Curve448, curveForm, Montgomery curve]
-
A.
curveOrder
Indicates the specific sequence or ranking assigned to curves within a set or system.
-
B.
curveEquationForm
Indicates that one entity is expressed as the mathematical equation or algebraic form that defines the shape or properties of a curve associated with another entity.
-
C.
curveEquationType
chosen
Indicates the specific mathematical form or classification of the equation that defines a curve.
-
D.
curveCondition
Indicates that a specific condition or constraint applies to a curve, such as its shape, smoothness, or allowable parameter range.
-
E.
curveEquation
Indicates that one entity is the mathematical equation that defines or represents the curve described by the other entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1 a.m.