Triple
T21802795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee for Postal Regulation |
E538277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit of CEPT |
C45323
|
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: organizational unit of CEPT Context triple: [Committee for Postal Regulation, instanceOf, organizational unit of CEPT]
-
A.
organizational unit of IEEE
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
-
B.
organizational unit designation
An organizational unit designation is a label or identifier that specifies a distinct division, department, or functional group within an organization’s structure.
-
C.
organizational unit category
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
D.
telecommunications organization
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.
-
E.
subsidiary body of ITU‑D
A subsidiary body of ITU‑D is an organizational entity established under the ITU Telecommunication Development Sector to carry out specialized tasks, studies, or advisory functions that support and implement ITU‑D’s development objectives and programs.
- F. None of above. chosen
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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.