Triple
T136955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Librarian of Congress |
E2767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal government position |
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 government position Context triple: [Librarian of Congress, instanceOf, federal government position]
-
A.
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.
-
B.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
C.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
-
D.
United States federal executive position
A United States federal executive position is an appointed or elected role within the executive branch of the federal government responsible for implementing and enforcing national laws, policies, and programs.
-
E.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.