Triple
T22056868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THEMIS instrument |
E545042
|
entity |
| Predicate | numberOfInfraredBands |
P123770
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [THEMIS instrument, numberOfInfraredBands, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInfraredBands Context triple: [THEMIS instrument, numberOfInfraredBands, 10]
-
A.
numberOfInfraredChannels
chosen
Indicates the count of distinct infrared channels associated with or supported by an entity.
-
B.
numberOfSpectralChannels
Indicates the relationship specifying how many distinct spectral channels are associated with an entity or measurement.
-
C.
numberOfFrequencyBands
Indicates the relationship specifying how many distinct frequency bands are associated with or used by an entity.
-
D.
hasSpectralChannel
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
E.
supportsInfraredConnectivity
Indicates that one entity provides or enables infrared-based communication or data transfer capabilities for another entity.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128588e0081909056ac8251afe935 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.