Triple
T32308504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lévy alpha-stable distribution |
E825429
|
entity |
| Predicate | locationParameterRange |
P28992
|
FINISHED |
| Object | δ ∈ ℝ |
—
|
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: δ ∈ ℝ | Statement: [Lévy alpha-stable distribution, locationParameterRange, δ ∈ ℝ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationParameterRange Context triple: [Lévy alpha-stable distribution, locationParameterRange, δ ∈ ℝ]
-
A.
latitudeRangeApproximate
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
-
B.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
C.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
E.
rangeDescription
Indicates the span or interval of values, positions, or extents over which something applies or is valid.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 1, 2026, 12:45 a.m.