Triple
T20471118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermite constant |
E502193
|
entity |
| Predicate | lowerBoundGrowth |
P140216
|
FINISHED |
| Object | Ω(n / 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 / log n) | Statement: [Hermite constant, lowerBoundGrowth, Ω(n / log n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundGrowth Context triple: [Hermite constant, lowerBoundGrowth, Ω(n / log n)]
-
A.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
B.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
-
C.
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.
-
D.
boundedByApprox
Indicates that one quantity is constrained by another within an approximate or tolerance-based bound, rather than an exact strict limit.
-
E.
lowerTerminus
Indicates that one entity serves as the lower endpoint or downstream terminus of another entity, such as a route, segment, or connection.
- F. None of above. chosen
Provenance (4 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699608d7c8190910217817e789915 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:33 a.m.