Triple
T33985461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegel’s lemma |
E871398
|
entity |
| Predicate | typicalBoundDependsOn |
—
|
GENERATED |
| Object | number of variables |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoundDependsOn Context triple: [Siegel’s lemma, typicalBoundDependsOn, number of variables]
-
A.
typicalBoundForm
Indicates that one entity is the standard or characteristic bound form in which another entity typically occurs or is represented.
-
B.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
givesBoundOn
chosen
Indicates that one quantity provides an upper or lower limit (a bound) on the value or behavior of another quantity.
-
D.
orderDependentBound
Indicates that one entity’s value or behavior is constrained by another in a way that depends on the specific ordering or sequence in which they are considered or applied.
-
E.
areBoundFrom
Indicates that one entity is constrained, limited, or restricted starting from a specified point, source, or condition.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.