Triple
T7921493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nernst–Lamp |
E183953
|
entity |
| Predicate | emitsSpectrum |
P79792
|
FINISHED |
| Object | continuous visible spectrum |
—
|
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: continuous visible spectrum | Statement: [Nernst–Lamp, emitsSpectrum, continuous visible spectrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emitsSpectrum Context triple: [Nernst–Lamp, emitsSpectrum, continuous visible spectrum]
-
A.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
-
B.
hasSpectralChannel
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
C.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
D.
notableFirstSpectrumTarget
Indicates that an entity is recognized as the first significant or historically important target observed or analyzed in a particular spectrum.
-
E.
neutronSpectrum
Indicates the energy distribution or range of neutrons present in a given system, interaction, or environment.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9499cc8190b6bd81f4625c77ab |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:06 p.m.