Triple
T2337730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H2S radar |
E44349
|
entity |
| Predicate | wavelengthBand |
P7244
|
FINISHED |
| Object | centimetric radar |
—
|
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: centimetric radar | Statement: [H2S radar, wavelengthBand, centimetric radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wavelengthBand Context triple: [H2S radar, wavelengthBand, centimetric radar]
-
A.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
C.
spectralRegion
chosen
Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
-
D.
primaryWavelength
Indicates the main or dominant wavelength associated with an entity, such as the principal wavelength at which it emits, reflects, or operates.
-
E.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.