Triple
T21963381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Collaboration with International Health Regulations Networks |
E542393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical collaboration centre |
C45584
|
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: technical collaboration centre Context triple: [Centre for Collaboration with International Health Regulations Networks, instanceOf, technical collaboration centre]
-
A.
technical commission
A technical commission is a specialized group of experts formally appointed to study, evaluate, and provide recommendations on complex technical or scientific matters within a specific domain.
-
B.
technical information service
A technical information service is a specialized support function that collects, manages, and delivers accurate, up-to-date technical data and guidance to users, customers, or internal stakeholders to assist with problem-solving and decision-making.
-
C.
technical services organization
A technical services organization is a specialized entity that provides expert engineering, IT, and other technology-focused support, solutions, and maintenance to help clients design, implement, and operate complex systems.
-
D.
technical emergency service
A technical emergency service is an organized unit that responds to and manages incidents involving technical hazards, infrastructure failures, and specialized rescue operations using expert equipment and skills.
-
E.
shared service centre
A shared service centre is a centralized organizational unit that consolidates and delivers common support functions (such as finance, HR, or IT) to multiple business units to improve efficiency, standardization, and cost-effectiveness.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:01 p.m.