Triple
T7570465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayleigh scattering |
E179225
|
entity |
| Predicate | scatters |
P2899
|
FINISHED |
| Object | electromagnetic radiation |
—
|
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: electromagnetic radiation | Statement: [Rayleigh scattering, scatters, electromagnetic radiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scatters Context triple: [Rayleigh scattering, scatters, electromagnetic radiation]
-
A.
ashesScatteredIn
Indicates that a deceased person's ashes have been dispersed at or within a specified location.
-
B.
scans
Indicates performing a systematic examination or inspection of something, often using a device or method to detect, read, or analyze its contents or structure.
-
C.
spreadBy
chosen
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
D.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
E.
crossDisperser
Indicates that one entity functions as a cross disperser, separating different wavelengths or components of another entity’s output or signal.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f920540c8190817712db5aa3eeff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.