Triple
T26966648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | typicalErrorBound |
P162835
|
FINISHED |
| Object | at most 1/3 |
—
|
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: at most 1/3 | Statement: [BPP, typicalErrorBound, at most 1/3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalErrorBound Context triple: [BPP, typicalErrorBound, at most 1/3]
-
A.
errorProbabilityBound
chosen
Indicates that there is an upper limit or constraint on the probability that an error will occur in a given process or system.
-
B.
typicalHorizontalAccuracy
Indicates the usual or expected degree of precision in the horizontal (x–y) position of a measurement or location estimate.
-
C.
relativeStandardUncertainty
Indicates the ratio of a measurement’s standard uncertainty to the measured value, expressing uncertainty relative to the magnitude of the quantity.
-
D.
typicalExponent
Indicates that one quantity serves as the characteristic or standard exponent associated with another quantity or expression.
-
E.
offsetStandardApprox
Indicates that one value serves as an approximate standard or baseline from which another value is offset or deviates.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 27, 2026, 6:36 a.m.