Triple
T432778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arecibo message |
E9748
|
entity |
| Predicate | transmissionFrequency |
P1685
|
FINISHED |
| Object | 2380 MHz |
—
|
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: 2380 MHz | Statement: [Arecibo message, transmissionFrequency, 2380 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionFrequency Context triple: [Arecibo message, transmissionFrequency, 2380 MHz]
-
A.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
B.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
C.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
D.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
E.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef084840819080653004b674cba8 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.