Triple
T3670046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amarna letters |
E77856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic correspondence |
C8738
|
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 correspondence Context triple: [Amarna letters, instanceOf, diplomatic correspondence]
-
A.
diplomatic cable
A diplomatic cable is a confidential, formal written communication sent between a country's diplomatic missions and its home government to report information, convey policy positions, or request instructions.
-
B.
diplomatic archive
chosen
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.
-
C.
diplomatic service
The diplomatic service is a governmental body of professional diplomats and support staff responsible for managing a nation's foreign relations, representing its interests abroad, and conducting negotiations with other states and international organizations.
-
D.
diplomatic convention
A diplomatic convention is a formal international agreement or treaty that establishes rules, procedures, or standards governing relations and conduct between states.
-
E.
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.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.