Triple
T20523493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mittag-Leffler function |
E503871
|
entity |
| Predicate | conditionOnParameter |
P84224
|
FINISHED |
| Object | α>0 |
—
|
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 | Statement: [Mittag-Leffler function, conditionOnParameter, α>0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnParameter Context triple: [Mittag-Leffler function, conditionOnParameter, α>0]
-
A.
containsCondition
chosen
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
B.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
modificationCondition
Indicates the specific circumstances or requirements under which a change or modification to something is permitted, triggered, or becomes applicable.
-
D.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
-
E.
conditionOnCoefficients
Indicates that one entity’s state, validity, or behavior is determined by or contingent upon the values of certain coefficients.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f471f18819091e8a57161fe0225 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.