Triple
T3562596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of the Kingdom of France |
E75372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical diplomatic agreements |
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: historical diplomatic agreements Context triple: [Treaties of the Kingdom of France, instanceOf, historical diplomatic agreements]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
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.
-
C.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
D.
diplomatic archive
A diplomatic archive is an organized collection of official records, correspondence, treaties, and related documents produced or received by a state's diplomatic services, preserved for legal, historical, and administrative purposes.
-
E.
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.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:21 p.m.