Triple
T10866354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Embassy |
E256540
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian diplomatic mission |
C401
|
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: Russian diplomatic mission Context triple: [Grand Embassy, instanceOf, Russian diplomatic mission]
-
A.
Russian diplomat
A Russian diplomat is an official representative of the Russian Federation who conducts negotiations, manages international relations, and protects Russia’s interests and citizens abroad through diplomatic channels.
-
B.
Japanese diplomatic mission
A Japanese diplomatic mission is an official government delegation, such as an embassy or consulate, representing Japan abroad to manage political, economic, cultural, and consular relations with the host country or international organization.
-
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.
diplomatic facility
chosen
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.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.