Triple
T25549994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordell curve |
E640411
|
entity |
| Predicate | isNonsingularFor |
P157315
|
FINISHED |
| Object | k ≠ 0 |
—
|
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: k ≠ 0 | Statement: [Mordell curve, isNonsingularFor, k ≠ 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonsingularFor Context triple: [Mordell curve, isNonsingularFor, k ≠ 0]
-
A.
isNonsingularIf
chosen
Indicates that something is nonsingular (e.g., invertible or non-degenerate) under a specified condition or set of conditions.
-
B.
forNonSingularPoint
Indicates that the relationship or condition applies only when the referenced point is not a single, isolated point (i.e., it is non-singular).
-
C.
isNondegenerate
Indicates that the object or structure has no trivial, collapsed, or singular cases and thus satisfies the required non-degeneracy conditions.
-
D.
isUnimodular
Indicates that a matrix (or linear transformation) has determinant ±1, preserving volume and invertibility over the integers.
-
E.
isNondegenerateOn
Indicates that a structure, form, or mapping does not collapse information or lose rank when restricted to a specified domain or subset.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 3:36 p.m.