Triple
T16690911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Advanced Radar for Subsurface and Ionosphere Sounding |
E405589
|
entity |
| Predicate | waveProperty |
P56830
|
FINISHED |
| Object | low frequency |
—
|
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: low frequency | Statement: [Mars Advanced Radar for Subsurface and Ionosphere Sounding, waveProperty, low frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveProperty Context triple: [Mars Advanced Radar for Subsurface and Ionosphere Sounding, waveProperty, low frequency]
-
A.
waveCharacteristic
chosen
Indicates that one entity specifies or describes a particular property or feature of a wave associated with another entity.
-
B.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
waveColor
Indicates the color associated with a particular wave (e.g., light or electromagnetic wave) in the described context.
-
D.
waveDirection
Indicates the direction in which a wave is propagating or traveling relative to a reference frame.
-
E.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea99bac8190a6c559ed7b7d8ecd |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.