Triple
T11219326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milnor number |
E265517
|
entity |
| Predicate | forMorseSingularity |
P97905
|
FINISHED |
| Object | μ = 1 |
—
|
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: μ = 1 | Statement: [Milnor number, forMorseSingularity, μ = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forMorseSingularity Context triple: [Milnor number, forMorseSingularity, μ = 1]
-
A.
hasMonodromy
Indicates that one mathematical object exhibits a monodromy action or structure with respect to another (typically along loops in a parameter or base space).
-
B.
museOf
Indicates that one entity serves as the source of artistic or intellectual inspiration for another.
-
C.
conjecturedSign
Indicates that one entity is proposed or hypothesized to be the sign, symbol, or indicator of another entity, without confirmed certainty.
-
D.
MOSCode
Indicates a relationship where a specific Military Occupational Specialty (MOS) code is assigned to or associated with an entity, such as a person, position, or role.
-
E.
multiplicity
Indicates the number of instances of one entity that can or must be associated with a single instance of another entity within a relationship.
- 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.