Triple
T35739742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorer 49 |
E1033000
|
entity |
| Predicate | frequencyRangeObserved |
P1685
|
FINISHED |
| Object | very low frequency radio waves |
—
|
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: very low frequency radio waves | Statement: [Explorer 49, frequencyRangeObserved, very low frequency radio waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyRangeObserved Context triple: [Explorer 49, frequencyRangeObserved, very low frequency radio waves]
-
A.
frequencyRegion
Indicates that something is associated with, occurs within, or is characterized by a particular range or band of frequencies.
-
B.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
C.
frequencyClass
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
D.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
E.
frequencyDependsOn
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.