Triple
T6858937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiener–Khinchin theorem |
E158222
|
entity |
| Predicate | inverseForm |
P9300
|
FINISHED |
| Object | R_X(τ) = ∫_{-∞}^{∞} S_X(f) e^{j2π f τ} df |
—
|
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: R_X(τ) = ∫_{-∞}^{∞} S_X(f) e^{j2π f τ} df | Statement: [Wiener–Khinchin theorem, inverseForm, R_X(τ) = ∫_{-∞}^{∞} S_X(f) e^{j2π f τ} df]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inverseForm
Context triple: [Wiener–Khinchin theorem, inverseForm, R_X(τ) = ∫_{-∞}^{∞} S_X(f) e^{j2π f τ} df]
-
A.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
B.
verseForm
Indicates the specific structural or metrical pattern in which a verse or poem is composed.
-
C.
inverseImage
Indicates the mapping from a set of outputs back to all inputs that are related to those outputs under a given function or relation.
-
D.
originalForm
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
E.
reversed
chosen
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
- 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.