Triple
T5660612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Searching for Interstellar Communications |
E124727
|
entity |
| Predicate | suggestsFrequencyNear |
P65602
|
FINISHED |
| Object | 1420 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: 1420 MHz | Statement: [Searching for Interstellar Communications, suggestsFrequencyNear, 1420 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suggestsFrequencyNear Context triple: [Searching for Interstellar Communications, suggestsFrequencyNear, 1420 MHz]
-
A.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
B.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
- F. None of above. chosen
Provenance (4 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0236af5308190b3d698eadf7bcd2b |
completed | March 22, 2026, 5:14 p.m. |
Created at: March 22, 2026, 3:42 p.m.