Triple
T9808435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imaging IR Spectrometer |
E238208
|
entity |
| Predicate | sensingMethod |
P47354
|
FINISHED |
| Object | passive remote sensing |
—
|
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: passive remote sensing | Statement: [Imaging IR Spectrometer, sensingMethod, passive remote sensing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensingMethod Context triple: [Imaging IR Spectrometer, sensingMethod, passive remote sensing]
-
A.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
B.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
C.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
D.
hasObservationMethod
chosen
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
-
E.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb21ef32c8190ab4b09d157798451 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.