Triple
T236453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplomatic Revolution of 1756 |
E4834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic event |
C238
|
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: diplomatic event Context triple: [Diplomatic Revolution of 1756, instanceOf, diplomatic event]
-
A.
diplomatic conference
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
B.
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.
-
C.
diplomatic relations
Diplomatic relations are the formal and informal interactions and agreements between sovereign states or international actors aimed at managing conflicts, fostering cooperation, and advancing mutual interests through negotiation and representation.
-
D.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
-
E.
political event
chosen
A political event is a planned or spontaneous occurrence involving political actors, institutions, or the public that aims to influence, express, or respond to political power, policy, or public opinion.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.