Triple
T23414788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffreys Gap |
E560174
|
entity |
| Predicate | observedInWavelengths |
P131838
|
FINISHED |
| Object | visible 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: visible light | Statement: [Jeffreys Gap, observedInWavelengths, visible light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInWavelengths Context triple: [Jeffreys Gap, observedInWavelengths, visible light]
-
A.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
B.
observedInElectromagneticSpectrum
chosen
Indicates that the subject is detected or measured within some region or band of the electromagnetic spectrum.
-
C.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
D.
hasSpectralObservation
Indicates that a spectral measurement or observation has been made of an entity, linking it to the corresponding spectral data or record.
-
E.
usedWavelengthRange
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a514b1d08190bbde2c3714c996fd |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.