Triple
T35506033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTRO-F |
E1026152
|
entity |
| Predicate | farInfraredSurveyorBands |
P131838
|
FINISHED |
| Object | far-infrared |
—
|
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: far-infrared | Statement: [ASTRO-F, farInfraredSurveyorBands, far-infrared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farInfraredSurveyorBands Context triple: [ASTRO-F, farInfraredSurveyorBands, far-infrared]
-
A.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
B.
observedInElectromagneticSpectrum
chosen
Indicates that the subject is detected or measured within some region or band of the electromagnetic spectrum.
-
C.
numberOfInfraredChannels
Indicates the count of distinct infrared channels associated with or supported by an entity.
-
D.
infraredExcess
Indicates that an object emits more infrared radiation than expected from its visible or thermal continuum, typically due to additional dust or circumstellar material.
-
E.
satelliteBand
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.