Triple
T34585774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheeger–Gromov compactness theorem |
E888038
|
entity |
| Predicate | limitObject |
P9149
|
FINISHED |
| Object | Riemannian manifold in smooth Cheeger–Gromov sense |
—
|
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: Riemannian manifold in smooth Cheeger–Gromov sense | Statement: [Cheeger–Gromov compactness theorem, limitObject, Riemannian manifold in smooth Cheeger–Gromov sense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitObject Context triple: [Cheeger–Gromov compactness theorem, limitObject, Riemannian manifold in smooth Cheeger–Gromov sense]
-
A.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
B.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
C.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
D.
isLimitOf
chosen
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
limitsDefinitionTo
Indicates that one entity constrains or narrows the scope of how another entity is defined or interpreted.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.