Triple
T6070465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUI Executive Agent |
E135267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal official role |
C312
|
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: federal official role Context triple: [CUI Executive Agent, instanceOf, federal official role]
-
A.
public official role
A public official role is a position of authority or responsibility within government or public institutions, empowered to make or influence decisions that affect the public interest.
-
B.
United States government official
A United States government official is an individual who holds an appointed or elected position within the federal, state, or local government of the United States, responsible for carrying out public duties and implementing laws and policies.
-
C.
officer of state
An officer of state is a high-ranking public official who holds a formal position within a government or monarchy, responsible for executing specific constitutional, administrative, or ceremonial duties of the state.
-
D.
United States federal government position
chosen
A United States federal government position is an official role within the executive, legislative, or judicial branches of the federal government, established by law or regulation to perform specific public duties and functions on behalf of the nation.
-
E.
great officer of state
A great officer of state is a high-ranking official who holds one of the most senior ceremonial or executive positions within a government or royal household, often with historic and constitutional significance.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.