Triple
T33419039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busemann function |
E855796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | function in metric geometry |
C18222
|
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: function in metric geometry Context triple: [Busemann function, instanceOf, function in metric geometry]
-
A.
theorem in metric number theory
A theorem in metric number theory is a rigorous statement describing the behavior of number-theoretic objects (such as Diophantine approximations or distribution of sequences) for "almost all" real numbers with respect to a given measure, typically Lebesgue measure.
-
B.
pseudometric
chosen
A pseudometric is a function that assigns a nonnegative real number as a "distance" between any two points in a set, satisfying all the axioms of a metric except that distinct points are allowed to have zero distance.
-
C.
geometric invariant
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
D.
geodesic structure
A geodesic structure is a framework composed of short, straight elements arranged along geodesic lines on a surface to create a lightweight, stable, and often dome-like form.
-
E.
result in metric Diophantine approximation
A result in metric Diophantine approximation is a theorem that describes how well almost all real numbers (with respect to a given measure) can be approximated by rationals or other structured sets, typically quantifying the size or frequency of exceptional sets.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.