Triple
T21848250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triangulum–Andromeda overdensity |
E539432
|
entity |
| Predicate | studiedInWavelength |
P90456
|
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: [Triangulum–Andromeda overdensity, studiedInWavelength, optical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiedInWavelength Context triple: [Triangulum–Andromeda overdensity, studiedInWavelength, optical]
-
A.
usedWavelengthRange
chosen
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
-
B.
wavelengthDependence
Indicates that one quantity or effect varies as a function of the wavelength of radiation or a wave.
-
C.
approximateWavelengthRange
Indicates the range of wavelengths that approximately characterizes or bounds the phenomenon, object, or interaction in question.
-
D.
observedInElectromagneticSpectrum
Indicates that the subject is detected or measured within some region or band of the electromagnetic spectrum.
-
E.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd56f4e081909a906b64c1019e6a |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.