Triple
T33629862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seiberg–Witten invariants |
E861521
|
entity |
| Predicate | wellDefinedWhen |
P176977
|
FINISHED |
| Object | b2^+ > 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: b2^+ > 1 | Statement: [Seiberg–Witten invariants, wellDefinedWhen, b2^+ > 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wellDefinedWhen Context triple: [Seiberg–Witten invariants, wellDefinedWhen, b2^+ > 1]
-
A.
wellPosedness
Indicates that a problem or system satisfies the conditions (such as existence, uniqueness, and stability of solutions) required to be considered mathematically well-posed.
-
B.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
C.
wasDefinedBy
Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85ad54881909afc34657322f20a |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.