Triple
T15918496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Ending problem |
E386030
|
entity |
| Predicate | improvedUpperBound |
P6555
|
FINISHED |
| Object | f(n) ≤ 2^{n+o(n)} |
—
|
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: f(n) ≤ 2^{n+o(n)} | Statement: [Happy Ending problem, improvedUpperBound, f(n) ≤ 2^{n+o(n)}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvedUpperBound
Context triple: [Happy Ending problem, improvedUpperBound, f(n) ≤ 2^{n+o(n)}]
-
A.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
B.
boundedByApprox
Indicates that one quantity is constrained by another within an approximate or tolerance-based bound, rather than an exact strict limit.
-
C.
givesBoundOn
Indicates that one quantity provides an upper or lower limit (a bound) on the value or behavior of another quantity.
-
D.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
E.
improvesOn
chosen
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
- 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.