Triple
T11219328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milnor number |
E265517
|
entity |
| Predicate | forFunction |
P23285
|
FINISHED |
| Object | f(z)=z^{k+1} has μ = k |
—
|
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: f(z)=z^{k+1} has μ = k | Statement: [Milnor number, forFunction, f(z)=z^{k+1} has μ = k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forFunction
Context triple: [Milnor number, forFunction, f(z)=z^{k+1} has μ = k]
-
A.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
B.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
C.
formFunction
Indicates that one entity’s physical form, structure, or configuration determines or enables the function or role performed by another (or by itself).
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
- 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_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. |
Created at: April 8, 2026, 9:30 p.m.