Triple
T3166675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Congressional and Intergovernmental Affairs of GSA |
E66227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liaison office |
C4033
|
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: liaison office Context triple: [Office of Congressional and Intergovernmental Affairs of GSA, instanceOf, liaison office]
-
A.
diplomatic facility
A diplomatic facility is a building or complex used by a nation or international organization to conduct official diplomatic activities, house diplomatic staff, and provide consular services in a host country.
-
B.
government liaison office
chosen
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
C.
diplomatic mission unit
A diplomatic mission unit is an organizational subdivision within a diplomatic mission responsible for carrying out specific functions such as political, economic, consular, cultural, or administrative activities in support of a state's foreign relations.
-
D.
diplomatic district
A diplomatic district is an urban area designated for embassies, consulates, international organizations, and related services that facilitate formal relations between states and global institutions.
-
E.
foreign affairs ministry
A foreign affairs ministry is a government department responsible for managing a country's international relations, diplomacy, and representation abroad.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.