Triple
T32310870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Support Program satellite |
E825493
|
entity |
| Predicate | hasSensorBand |
P117574
|
FINISHED |
| Object | 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: infrared | Statement: [Defense Support Program satellite, hasSensorBand, infrared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSensorBand Context triple: [Defense Support Program satellite, hasSensorBand, infrared]
-
A.
sensorBand
chosen
Indicates that an entity is associated with or operates within a specific sensor frequency band or range.
-
B.
hasHeartRateSensor
Indicates that an entity is equipped with or includes a heart rate sensing capability or device.
-
C.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
D.
hasBluetooth
Indicates that one entity is equipped with or supports Bluetooth connectivity.
-
E.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 1, 2026, 12:46 a.m.