Triple
T11219327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milnor number |
E265517
|
entity |
| Predicate | forNonSingularPoint |
P97906
|
FINISHED |
| Object | μ = 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: μ = 0 | Statement: [Milnor number, forNonSingularPoint, μ = 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forNonSingularPoint Context triple: [Milnor number, forNonSingularPoint, μ = 0]
-
A.
hasCoordinateSingularity
Indicates that something possesses a point or region where its coordinate description becomes undefined or degenerate, even if the underlying object or space may remain well-behaved.
-
B.
isNondegenerate
Indicates that the object or structure has no trivial, collapsed, or singular cases and thus satisfies the required non-degeneracy conditions.
-
C.
isNondegenerateOn
Indicates that a structure, form, or mapping does not collapse information or lose rank when restricted to a specified domain or subset.
-
D.
isNonzeroFor
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
E.
nonDifferentiableAt
Indicates that a function fails to have a well-defined derivative at a specific point.
- F. None of above. chosen
Provenance (4 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8eb84c48190b4f3bede254afde2 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.