Triple
T2706441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephan's Quintet |
E59351
|
entity |
| Predicate | observedInWavelength |
P38137
|
FINISHED |
| Object | optical |
—
|
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: optical | Statement: [Stephan's Quintet, observedInWavelength, optical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInWavelength Context triple: [Stephan's Quintet, observedInWavelength, optical]
-
A.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
B.
observingBand
chosen
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
C.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
D.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
E.
primaryWavelength
Indicates the main or dominant wavelength associated with an entity, such as the principal wavelength at which it emits, reflects, or operates.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda725f24819090e8d936b3d2d5bc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.