Triple
T3195244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Registry of the Inter-American Court of Human Rights |
E66919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical support office |
C11050
|
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 support office Context triple: [Registry of the Inter-American Court of Human Rights, instanceOf, technical support office]
-
A.
public office
A public office is an official position of authority and responsibility within a government or public institution, held to serve the interests and welfare of the public under established laws and regulations.
-
B.
information technology division
The information technology division is the organizational unit responsible for planning, implementing, managing, and supporting an institution’s technology infrastructure, systems, and services to enable its operational and strategic goals.
-
C.
clerical office
A clerical office is a workplace where administrative tasks such as record-keeping, correspondence, data entry, and document management are performed to support an organization’s operations.
-
D.
shared service centre
chosen
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.
-
E.
computer services company
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:07 p.m.