Triple
T4638375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Family Compact |
E101589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century diplomatic agreement |
C566
|
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: 18th-century diplomatic agreement Context triple: [Third Family Compact, instanceOf, 18th-century diplomatic agreement]
-
A.
World War I–era diplomatic agreement
A World War I–era diplomatic agreement is a formal treaty, pact, or understanding negotiated between states during or immediately surrounding the First World War, aimed at managing alliances, territorial claims, military commitments, or postwar settlements.
-
B.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
C.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
early 18th-century conflict
An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.