Triple
T23142470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodge Laplacian |
E577497
|
entity |
| Predicate | kernelConsistsOf |
P151071
|
FINISHED |
| Object | harmonic forms |
—
|
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: harmonic forms | Statement: [Hodge Laplacian, kernelConsistsOf, harmonic forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kernelConsistsOf Context triple: [Hodge Laplacian, kernelConsistsOf, harmonic forms]
-
A.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
-
B.
kernelDependsOn
Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
-
C.
kernelVersion
Indicates the specific operating system kernel version associated with an entity.
-
D.
kernelMainlineStatus
Indicates whether something is part of, aligned with, or supported by the mainline (upstream) version of a kernel.
-
E.
KernelFoundedIn
Indicates that a kernel (such as an operating system kernel or similar core software component) was established, created, or first introduced in a specific time or place.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecb72fc8190a24e8f5756217a36 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4 p.m.