Triple
T6854896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian legation in Washington, D.C. |
E158112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legation |
C21694
|
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: legation Context triple: [Russian legation in Washington, D.C., instanceOf, legation]
-
A.
state delegation
State delegation is the process by which a government transfers specific powers, responsibilities, or decision-making authority from a central level to subordinate entities such as regional authorities, agencies, or private actors while retaining ultimate sovereignty.
-
B.
appointing authority
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
-
C.
delegate to the Continental Congress
A delegate to the Continental Congress is an appointed or elected representative from one of the American colonies who participated in the intercolonial legislative assemblies that coordinated resistance to British rule and laid the groundwork for the United States’ independence.
-
D.
declaration
A declaration is a statement in a program that introduces an identifier (such as a variable, function, or type) and specifies its properties without necessarily providing its full implementation.
-
E.
executive authority
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:20 p.m.