Triple
T24336915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochner–Martinelli formula |
E613405
|
entity |
| Predicate | kernelProperty |
P155759
|
FINISHED |
| Object | (n,n-1)-form |
—
|
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: (n,n-1)-form | Statement: [Bochner–Martinelli formula, kernelProperty, (n,n-1)-form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kernelProperty Context triple: [Bochner–Martinelli formula, kernelProperty, (n,n-1)-form]
-
A.
kernelConsistsOf
Indicates that a kernel is composed of or made up from the specified constituent elements or components.
-
B.
nuclearProperty
Indicates a relationship where an entity possesses or is characterized by a specific nuclear-related attribute, such as structure, behavior, or interaction at the atomic nucleus level.
-
C.
kernelType
Indicates the specific kind or category of kernel associated with or used by an entity.
-
D.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
-
E.
kernelDefines
Indicates that a kernel (core component or subsystem) specifies or establishes the structure, behavior, or rules governing another element.
- F. None of above. chosen
Provenance (4 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293212a0881908da028e81d26247d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:57 a.m.