Triple
T32308526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lévy alpha-stable distribution |
E825429
|
entity |
| Predicate | meanExistsCondition |
P67472
|
FINISHED |
| Object | mean exists only if α > 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: mean exists only if α > 1 | Statement: [Lévy alpha-stable distribution, meanExistsCondition, mean exists only if α > 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanExistsCondition Context triple: [Lévy alpha-stable distribution, meanExistsCondition, mean exists only if α > 1]
-
A.
existsIf
chosen
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
B.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
C.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
-
D.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
E.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
- 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_69f6bd89d3dc8190988bb54d492fd4a5 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.