Triple
T31703481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | q-Gaussian distribution |
E809119
|
entity |
| Predicate | hasInfiniteVariance |
P46239
|
FINISHED |
| Object | for 5/3 ≤ q < 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: for 5/3 ≤ q < 3 | Statement: [q-Gaussian distribution, hasInfiniteVariance, for 5/3 ≤ q < 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfiniteVariance Context triple: [q-Gaussian distribution, hasInfiniteVariance, for 5/3 ≤ q < 3]
-
A.
hasFiniteVarianceCondition
Indicates that a specified random variable or distribution satisfies the condition of having a finite variance.
-
B.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
C.
hasFiniteMomentsOfAllOrders
Indicates that a random variable or distribution has finite expected values for all positive integer powers (moments) of it.
-
D.
isInfinitelyDivisible
Indicates that something can be divided into smaller parts without any theoretical limit on the number of divisions.
-
E.
isInfinite
chosen
Indicates that something has no finite limit, bound, or endpoint in size, extent, or duration.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: April 30, 2026, 11:13 p.m.