Triple
T32308501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lévy alpha-stable distribution |
E825429
|
entity |
| Predicate | stabilityParameterRange |
P174165
|
FINISHED |
| Object | 0 < α ≤ 2 |
—
|
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: 0 < α ≤ 2 | Statement: [Lévy alpha-stable distribution, stabilityParameterRange, 0 < α ≤ 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilityParameterRange Context triple: [Lévy alpha-stable distribution, stabilityParameterRange, 0 < α ≤ 2]
-
A.
stabilityRegion
Indicates the set of conditions or parameter values under which a system, process, or configuration remains stable.
-
B.
haveStabilityDeterminedBy
Indicates that the stability of one entity is determined or governed by another specified factor or entity.
-
C.
stabilityDescription
Indicates how stable, consistent, or enduring the relationship, condition, or state between the entities is over time.
-
D.
stabilityCharacteristic
Indicates that one entity specifies a property or feature related to the stability or steadiness of another entity or system.
-
E.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
- 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_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:45 a.m.