Triple
T18609441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic–Eurasian cable network |
E454850
|
entity |
| Predicate | dataTypeTransmitted |
P132771
|
FINISHED |
| Object | telegraph signals |
—
|
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: telegraph signals | Statement: [North Atlantic–Eurasian cable network, dataTypeTransmitted, telegraph signals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeTransmitted Context triple: [North Atlantic–Eurasian cable network, dataTypeTransmitted, telegraph signals]
-
A.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
C.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
dataTransferType
Indicates the method or mode by which data is transmitted or exchanged between entities.
-
E.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d0048b08190a7dd407f14d95799 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.