Triple
T5425437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sperner's lemma |
E121351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in combinatorial topology |
C10468
|
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: result in combinatorial topology Context triple: [Sperner's lemma, instanceOf, result in combinatorial topology]
-
A.
result in topology
chosen
A result in topology is a proven theorem or proposition that describes how topological properties and structures behave or relate under specified conditions.
-
B.
topological game
A topological game is a two-player game played on a topological space where players alternately choose points, sets, or open neighborhoods according to specified rules, with winning conditions defined by topological properties such as convergence, closure, or covering.
-
C.
combinatorial game
A combinatorial game is a two-player, perfect-information game with no chance elements where players move alternately and the outcome depends solely on their strategic choices under well-defined rules.
-
D.
result in convex analysis
In convex analysis, a result is a formally stated and proven fact—such as a theorem, lemma, or proposition—that characterizes properties or relationships of convex sets, convex functions, or related optimization structures.
-
E.
result in complex analysis
A result in complex analysis is a proven statement or theorem about functions of a complex variable, often revealing deep relationships between analytic, geometric, and topological properties in the complex plane.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.