Triple
T2396745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau for Management (USAID) |
E47668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative support bureau |
C9619
|
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: administrative support bureau Context triple: [Bureau for Management (USAID), instanceOf, administrative support bureau]
-
A.
bureau-level office
chosen
A bureau-level office is an organizational unit within a larger department or agency that operates at the bureau tier, managing specialized programs, policies, or services under that bureau’s authority.
-
B.
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.
-
C.
judicial administrative office
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
D.
academic administrative office
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
E.
colonial administrative service
A colonial administrative service is a bureaucratic organization established by a colonial power to govern, manage, and implement policies in its overseas territories.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:57 p.m.