Triple
T6508425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of the Dutch Republic |
E150068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical diplomatic phenomenon |
C16758
|
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: historical diplomatic phenomenon Context triple: [Treaties of the Dutch Republic, instanceOf, historical diplomatic phenomenon]
-
A.
diplomatic history
chosen
Diplomatic history is the study of how states and other international actors conduct relations, negotiate agreements, and manage conflicts over time through diplomacy and foreign policy.
-
B.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
C.
diplomatic incident
A diplomatic incident is an event or action involving representatives of different states that causes tension, conflict, or embarrassment in their official relations.
-
D.
diplomatic issue
A diplomatic issue is a matter of contention or concern between states or international actors that requires negotiation, communication, or policy decisions to manage or resolve.
-
E.
historical relationship
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:43 p.m.