Triple

T2489607
Position Surface form Disambiguated ID Type / Status
Subject Philip Vian E52006 entity
Predicate participatedIn P149 FINISHED
Object Altmark incident E1520 NE 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: Altmark incident | Statement: [Philip Vian, participatedIn, Altmark incident]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Altmark incident
Context triple: [Philip Vian, participatedIn, Altmark incident]
  • A. Altmark Incident chosen
    The Altmark Incident was a 1940 World War II naval confrontation in Norwegian waters, where British forces boarded the German tanker Altmark to free imprisoned Allied sailors, heightening tensions during the early "Phoney War" period.
  • B. Sian Incident
    The Sian Incident was a 1936 political crisis in China in which Generalissimo Chiang Kai-shek was detained by his own generals, leading to a negotiated United Front between the Nationalists and Communists against Japanese aggression.
  • C. Tapani Incident
    The Tapani Incident was a major 1915 anti-Japanese uprising in southern Taiwan, led by local religious and militia leaders, and is remembered as one of the most significant resistance movements during Japanese colonial rule.
  • D. Imo Incident
    The Imo Incident was an 1882 mutiny of Korean soldiers in Seoul that escalated into violent unrest and foreign intervention, highlighting Korea’s internal instability and vulnerability to outside powers.
  • E. Panjdeh incident
    The Panjdeh incident was an 1885 military clash between the Russian Empire and Afghanistan that nearly triggered war with Britain and marked a critical flashpoint in the Anglo-Russian rivalry in Central Asia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ab4955111c8190835bf619adec21ff completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd17b7a048190bcc8f0a66514a052 completed March 7, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69af2b8429388190a2d1b1610511ea75 completed March 9, 2026, 8:20 p.m.
Created at: March 6, 2026, 9:45 p.m.