Triple
T21509008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian postal and telegraph administration |
E530667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telegraph administration |
C16705
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: telegraph administration Context triple: [Imperial Russian postal and telegraph administration, instanceOf, telegraph administration]
-
A.
telegraph operator
A telegraph operator is a person who sends, receives, and decodes messages transmitted over telegraph systems using coded signals such as Morse code.
-
B.
postal administration
A postal administration is the governmental or authorized organization responsible for managing and operating a country’s postal services, including mail collection, processing, transportation, and delivery.
-
C.
telecommunications organization
chosen
A telecommunications organization is an entity that provides communication services and infrastructure—such as voice, data, and internet connectivity—across distances using wired, wireless, or satellite networks.
-
D.
arts administrator
An arts administrator is a professional who manages the business, organizational, and strategic aspects of arts organizations, such as theaters, galleries, and cultural institutions, to support and promote artistic programs and initiatives.
-
E.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
- F. None of above.
Provenance (1 batch)
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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:25 p.m.