Triple
T35476245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corfu Channel incident |
E1025341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Kingdom–Albania relations event |
C65979
|
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: United Kingdom–Albania relations event Context triple: [Corfu Channel incident, instanceOf, United Kingdom–Albania relations event]
-
A.
Iran–United Kingdom relations event
An Iran–United Kingdom relations event is a specific historical or contemporary occurrence that significantly affects the diplomatic, political, economic, or cultural relationship between Iran and the United Kingdom.
-
B.
Iraq–United Nations relations event
An Iraq–United Nations relations event is an occurrence or series of actions involving diplomatic, political, humanitarian, or security interactions between Iraq and the United Nations that significantly affects their bilateral relationship.
-
C.
United States–Russia relations event
A United States–Russia relations event is a specific occurrence, interaction, or development that significantly affects the political, diplomatic, military, economic, or cultural relationship between the United States and Russia.
-
D.
EU–US relations event
An EU–US relations event is a diplomatic, political, or economic occurrence that significantly affects the interactions, policies, or strategic partnership between the European Union and the United States.
-
E.
France–Japan relations event
A France–Japan relations event is a diplomatic, cultural, economic, or political occurrence that significantly involves and affects the bilateral relationship between France and Japan.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.