Triple
T12639363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars 3 |
E301850
|
entity |
| Predicate | telemetryBand |
P47328
|
FINISHED |
| Object | radio communications |
—
|
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: radio communications | Statement: [Mars 3, telemetryBand, radio communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telemetryBand Context triple: [Mars 3, telemetryBand, radio communications]
-
A.
transmissionBand
chosen
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
B.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
C.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
D.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.