Triple
T4347590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fashoda Incident |
E97942
|
entity |
| Predicate | diplomaticMethodUsed |
P18759
|
FINISHED |
| Object | negotiation |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: negotiation | Statement: [Fashoda Incident, diplomaticMethodUsed, negotiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticMethodUsed Context triple: [Fashoda Incident, diplomaticMethodUsed, negotiation]
-
A.
diplomaticOutcome
Indicates the result or consequence of a diplomatic interaction, negotiation, or relationship between parties.
-
B.
diplomaticActivity
Indicates engagement in formal or informal diplomatic actions or interactions between parties, such as negotiations, consultations, or representation.
-
C.
diplomaticPolicy
Indicates the stance, strategy, or set of guiding principles an entity adopts in managing its diplomatic relations and interactions with others.
-
D.
diplomaticPost
Indicates that an entity holds or is assigned to an official diplomatic position or mission representing one state or organization to another.
-
E.
usedInDiplomacy
chosen
Indicates that something is employed as a tool, method, or resource within diplomatic interactions or negotiations between parties.
- F. None of above.
Provenance (3 batches)
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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a5559c819081608b0aaf6a0e66 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.