Triple
T20465800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VisAO camera |
E502044
|
entity |
| Predicate | observesInBand |
P38137
|
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: [VisAO camera, observesInBand, visible light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesInBand Context triple: [VisAO camera, observesInBand, visible light]
-
A.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
B.
observingBand
chosen
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
C.
visibleInBand
Indicates that something can be observed or detected within a specified spectral band or range of wavelengths.
-
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.
observesIn
Indicates that one entity observes, monitors, or takes note of another entity within a specific context, environment, or scope.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696aa0794819082c9989b1f7e9f37 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.