Triple
T32541791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night light |
E831731
|
entity |
| Predicate | affectsLightSpectrum |
P69537
|
FINISHED |
| Object | blue light |
—
|
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: blue light | Statement: [Night light, affectsLightSpectrum, blue light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsLightSpectrum Context triple: [Night light, affectsLightSpectrum, blue light]
-
A.
emitsSpectrum
Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
-
B.
hasLightingEffect
chosen
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
-
C.
emitsWavelength
Indicates that one entity produces or gives off electromagnetic radiation at a specified wavelength associated with another entity.
-
D.
sensitivityToLight
Indicates a relationship where an entity reacts adversely or more strongly than normal when exposed to light.
-
E.
canLight
Indicates that one entity has the ability or capacity to provide or emit light to another entity or environment.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:02 a.m.