Triple
T3073818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Neighbor policy |
E64089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic policy |
C12226
|
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 policy Context triple: [Good Neighbor policy, instanceOf, diplomatic policy]
-
A.
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.
-
B.
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.
-
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 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.
diplomatic initiative
A diplomatic initiative is a coordinated effort by one or more states or international actors to open, advance, or resolve political, economic, or security issues through negotiation and dialogue rather than coercion or conflict.
- F. None of above. chosen
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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.