Triple
T37105645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 245409 |
E918832
|
entity |
| Predicate | hasSenderOfMessage |
P26492
|
FINISHED |
| Object | Earth-based radio transmitter |
—
|
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: Earth-based radio transmitter | Statement: [HD 245409, hasSenderOfMessage, Earth-based radio transmitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSenderOfMessage Context triple: [HD 245409, hasSenderOfMessage, Earth-based radio transmitter]
-
A.
hasMessageSender
chosen
Indicates that one entity is the sender or originator of a given message.
-
B.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
C.
hasFirstRecipient
Indicates that an entity is the initial or primary recipient of something (such as a message, award, or transfer) in a sequence or set of recipients.
-
D.
hasRecipientRole
Indicates that a specified entity serves as the recipient or target role in a given interaction, transaction, or relationship.
-
E.
hasMessageFlow
Indicates a directional communication or information exchange relationship where one entity sends a message to another.
- 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_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: May 3, 2026, 4:14 p.m.