Triple
T15918531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdős–Szekeres theorem |
E386031
|
entity |
| Predicate | originalBound |
P96513
|
FINISHED |
| Object | ES(n) ≤ \binom{2n-4}{n-2} + 1 |
—
|
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: ES(n) ≤ \binom{2n-4}{n-2} + 1 | Statement: [Erdős–Szekeres theorem, originalBound, ES(n) ≤ \binom{2n-4}{n-2} + 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBound
Context triple: [Erdős–Szekeres theorem, originalBound, ES(n) ≤ \binom{2n-4}{n-2} + 1]
-
A.
givesBoundOn
chosen
Indicates that one quantity provides an upper or lower limit (a bound) on the value or behavior of another quantity.
-
B.
oftenBoundIn
Indicates that one entity is frequently enclosed, packaged, or contained within another entity.
-
C.
originalExtent
Indicates the total size or scope that something initially had before any reduction, alteration, or loss.
-
D.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
E.
boundedByApprox
Indicates that one quantity is constrained by another within an approximate or tolerance-based bound, rather than an exact strict limit.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.