Triple
T24957061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiener–Hopf equations |
E624504
|
entity |
| Predicate | typicalKernel |
P5103
|
FINISHED |
| Object | convolution kernel |
—
|
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: convolution kernel | Statement: [Wiener–Hopf equations, typicalKernel, convolution kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalKernel Context triple: [Wiener–Hopf equations, typicalKernel, convolution kernel]
-
A.
typicalKernelABI
Indicates that one entity uses or conforms to the other entity as its standard or default kernel-level application binary interface (ABI).
-
B.
primaryKernelType
Indicates that one entity is the main or default kernel type associated with another entity.
-
C.
kernelType
chosen
Indicates the specific kind or category of kernel associated with or used by an entity.
-
D.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
E.
kernelConsistsOf
Indicates that a kernel is composed of or made up from the specified constituent elements or components.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 18, 2026, 5:58 a.m.