Triple
T22423282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdős distinct distances problem |
E554301
|
entity |
| Predicate | originalUpperBoundConstruction |
P14327
|
FINISHED |
| Object | n / sqrt(log 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: n / sqrt(log n) | Statement: [Erdős distinct distances problem, originalUpperBoundConstruction, n / sqrt(log n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUpperBoundConstruction Context triple: [Erdős distinct distances problem, originalUpperBoundConstruction, n / sqrt(log n)]
-
A.
isUpperBoundFor
chosen
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.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
C.
boundedSuperiorlyBy
Indicates that one entity serves as the upper or top boundary limit of another entity.
-
D.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2af620819083338127e78137dc |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:47 p.m.