Triple
T32308502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lévy alpha-stable distribution |
E825429
|
entity |
| Predicate | skewnessParameterRange |
P173952
|
FINISHED |
| Object | −1 ≤ β ≤ 1 |
—
|
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: −1 ≤ β ≤ 1 | Statement: [Lévy alpha-stable distribution, skewnessParameterRange, −1 ≤ β ≤ 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skewnessParameterRange Context triple: [Lévy alpha-stable distribution, skewnessParameterRange, −1 ≤ β ≤ 1]
-
A.
slopeAngleRange
Indicates the range of possible or allowed slope angles associated with a given entity or context.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
D.
typicalRangeClass
Indicates that the related entity belongs to a class whose members typically fall within a characteristic or expected value range.
-
E.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd8835588190b562ff2832f98acf |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:45 a.m.