Triple
T19040443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poldhu Wireless Station |
E465984
|
entity |
| Predicate | transmittedSignalContent |
P58686
|
FINISHED |
| Object | Morse code letter S |
—
|
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: Morse code letter S | Statement: [Poldhu Wireless Station, transmittedSignalContent, Morse code letter S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmittedSignalContent Context triple: [Poldhu Wireless Station, transmittedSignalContent, Morse code letter S]
-
A.
signalContent
chosen
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
-
B.
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.
-
C.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
D.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
E.
dataCarried
Indicates that some data is transported, transmitted, or conveyed by a particular medium, channel, or entity.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80054c88190a9d3a49aed504235 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.