Triple
T37105644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 245409 |
E918832
|
entity |
| Predicate | hasMediumOfMessage |
P7961
|
FINISHED |
| Object | 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: radio waves | Statement: [HD 245409, hasMediumOfMessage, radio waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediumOfMessage Context triple: [HD 245409, hasMediumOfMessage, radio waves]
-
A.
hasMediumCharacter
Indicates that one entity possesses or is associated with a character whose size, intensity, or degree is classified as medium.
-
B.
hasAssociatedMedium
chosen
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
C.
hasMediaForm
Indicates that something is associated with, presented in, or exists as a particular medium or media format.
-
D.
hasIntendedMedium
Indicates that an entity is associated with a medium or format it is designed, planned, or meant to be presented or communicated through.
-
E.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.