Triple
T8399569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresnel integrals |
E198136
|
entity |
| Predicate | behaviorAtMinusInfinity |
P6112
|
FINISHED |
| Object | C(-∞) = -1/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: C(-∞) = -1/2 | Statement: [Fresnel integrals, behaviorAtMinusInfinity, C(-∞) = -1/2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorAtMinusInfinity Context triple: [Fresnel integrals, behaviorAtMinusInfinity, C(-∞) = -1/2]
-
A.
finiteAt
Indicates that a function, quantity, or value remains finite (not infinite or undefined) at a specified point or under a given condition.
-
B.
divergesAt
Indicates that a process, function, or behavior fails to converge or terminate at a specific point or under specific conditions.
-
C.
limitBehavior
chosen
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
D.
derivativeForNegativeInput
Indicates that the derivative of a function is being evaluated or defined specifically for negative input values of its independent variable.
-
E.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824bfcbc8190b26bfcb5f8c4777c |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.