Triple
T32030616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calderón reproducing formula |
E817946
|
entity |
| Predicate | conditionOnWavelet |
P130541
|
FINISHED |
| Object | admissibility condition |
—
|
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: admissibility condition | Statement: [Calderón reproducing formula, conditionOnWavelet, admissibility condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnWavelet Context triple: [Calderón reproducing formula, conditionOnWavelet, admissibility condition]
-
A.
waveCondition
chosen
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
B.
canCondition
Indicates that one entity has the capability or potential to impose, apply, or bring about a particular condition on another entity or situation.
-
C.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
D.
conditionWhenFound
Indicates the state or circumstances that were present at the time the entity was first discovered or observed.
-
E.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:18 a.m.