Triple
T22328638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strominger–Yau–Zaslow conjecture |
E551966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conjecture in mirror symmetry |
C11421
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: conjecture in mirror symmetry Context triple: [Strominger–Yau–Zaslow conjecture, instanceOf, conjecture in mirror symmetry]
-
A.
mathematical conjecture
chosen
A mathematical conjecture is a proposed statement or proposition, based on observed patterns or partial evidence, that is believed to be true but has not yet been rigorously proven or disproven.
-
B.
set of mathematical conjectures
A set of mathematical conjectures is a collection of unproven but plausibly true mathematical statements, typically related by topic, structure, or underlying theory.
-
C.
conjecture in number theory
A conjecture in number theory is an unproven but plausibly true statement about the properties or relationships of integers, often motivated by patterns, partial results, or computational evidence.
-
D.
geodesic in moduli space
A geodesic in moduli space is the locally length-minimizing path (with respect to a chosen natural metric, such as the Weil–Petersson metric) that describes the most efficient deformation of complex structures or geometric data between two points in the moduli space.
-
E.
problem in invariant theory
A problem in invariant theory concerns determining and characterizing the algebraic functions (invariants) that remain unchanged under the action of a given group on a vector space or algebraic variety.
- F. None of above.
Provenance (1 batch)
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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.