Triple
T13203602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOS |
E314300
|
entity |
| Predicate | canBeTransmittedBy |
P4409
|
FINISHED |
| Object | radio |
—
|
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 | Statement: [SOS, canBeTransmittedBy, radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTransmittedBy Context triple: [SOS, canBeTransmittedBy, radio]
-
A.
isTransmittedBy
chosen
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
-
B.
modeOfTransmission
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
-
C.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
D.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
-
E.
canBeRelayedOver
Indicates that one entity (such as a signal, message, or connection) is capable of being transmitted or forwarded via another entity (such as a medium, channel, or network).
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9961a48190a1157df47f59b7af |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.