Triple
T23142476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodge Laplacian |
E577497
|
entity |
| Predicate | spectrum |
P151072
|
FINISHED |
| Object | discrete on compact manifolds |
—
|
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: discrete on compact manifolds | Statement: [Hodge Laplacian, spectrum, discrete on compact manifolds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectrum Context triple: [Hodge Laplacian, spectrum, discrete on compact manifolds]
-
A.
emitsSpectrum
Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
-
B.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
-
C.
observedInElectromagneticSpectrum
Indicates that the subject is detected or measured within some region or band of the electromagnetic spectrum.
-
D.
operatedInSpectrum
Indicates that an entity functioned or carried out its operations within a specified portion or range of the electromagnetic spectrum.
-
E.
spectrumOfActivity
Indicates the range and variety of targets, conditions, or effects over which an action, agent, or process is effective or operative.
- 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.