Triple
T19532113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamming bound |
E488680
|
entity |
| Predicate | upperBounds |
P14327
|
FINISHED |
| Object | size of a code with given parameters |
—
|
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: size of a code with given parameters | Statement: [Hamming bound, upperBounds, size of a code with given parameters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperBounds Context triple: [Hamming bound, upperBounds, size of a code with given parameters]
-
A.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
B.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
C.
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.
-
D.
boundedSuperiorlyBy
Indicates that one entity serves as the upper or top boundary limit of another entity.
-
E.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363fd1f8819080805346efad2579 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.