Triple
T15918532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdős–Szekeres theorem |
E386031
|
entity |
| Predicate | lowerBound |
P75151
|
FINISHED |
| Object | ES(n) ≥ 2^{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) ≥ 2^{n-2} + 1 | Statement: [Erdős–Szekeres theorem, lowerBound, ES(n) ≥ 2^{n-2} + 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBound
Context triple: [Erdős–Szekeres theorem, lowerBound, ES(n) ≥ 2^{n-2} + 1]
-
A.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
B.
lowerValueIndicates
Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
-
C.
hasLowerBoundaryDefinedBy
Indicates that one entity’s lower limit, edge, or boundary is specified or determined by another entity.
-
D.
isBoundedBelow
chosen
Indicates that every value in a set or function is greater than or equal to some fixed lower bound.
-
E.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
- 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.