Triple
T30242449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hughes telegraph system |
E768953
|
entity |
| Predicate | transmissionRate |
P195234
|
FINISHED |
| Object | up to 60 words per minute |
—
|
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: up to 60 words per minute | Statement: [Hughes telegraph system, transmissionRate, up to 60 words per minute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionRate Context triple: [Hughes telegraph system, transmissionRate, up to 60 words per minute]
-
A.
transmissionFactor
Indicates how strongly or efficiently something is passed or transmitted from one entity to another.
-
B.
spreadingRateType
Indicates the manner or category of how quickly or in what way something spreads or propagates.
-
C.
transmissionPattern
Indicates how something is passed or spread from one entity to another, such as the mode or route of transmission.
-
D.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
E.
modeOfTransmission
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: April 29, 2026, 7:39 p.m.