Triple
T19532118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamming bound |
E488680
|
entity |
| Predicate | isInequality |
P105609
|
FINISHED |
| Object | M * V_q(n,t) ≤ q^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: M * V_q(n,t) ≤ q^n | Statement: [Hamming bound, isInequality, M * V_q(n,t) ≤ q^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInequality Context triple: [Hamming bound, isInequality, M * V_q(n,t) ≤ q^n]
-
A.
satisfiesInequality
chosen
Indicates that one quantity or expression fulfills the condition specified by a given inequality relation (such as <, ≤, >, or ≥).
-
B.
inequality
Indicates that there is a difference or lack of equality in status, rights, opportunities, or treatment between entities.
-
C.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
D.
dataProcessingInequality
Indicates that processing data through a (possibly noisy) transformation cannot increase the information one variable has about another, so the mutual information between them can only stay the same or decrease.
-
E.
isInconsistent
Indicates that there is a logical or factual contradiction within or between the entities or statements involved.
- 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.