Triple

T1971569
Position Surface form Disambiguated ID Type / Status
Subject Kronstadt E42812 entity
Predicate hasFortification P8412 FINISHED
Object Kronstadt Fortress E42812 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: Kronstadt Fortress | Statement: [Kronstadt, hasFortification, Kronstadt Fortress]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kronstadt Fortress
Context triple: [Kronstadt, hasFortification, Kronstadt Fortress]
  • A. Kronstadt chosen
    Kronstadt is a historic Russian naval port and fortress city located on Kotlin Island near Saint Petersburg, long serving as a key base for the Russian Baltic Fleet.
  • B. Shlisselburg
    Shlisselburg is a historic Russian town near Saint Petersburg, best known for its strategic fortress and former political prison on Lake Ladoga.
  • C. Brest Fortress
    Brest Fortress is a historic 19th-century Russian fortress in Brest, Belarus, renowned for its fierce Soviet resistance during the early days of the German invasion in World War II.
  • D. Sevastopol
    Sevastopol is a major port city on the Black Sea, historically significant as a naval base and the site of key military conflicts.
  • E. Petrovsk-Port
    Petrovsk-Port was a significant port city in the Russian Empire’s Caucasus region, serving as an important commercial and strategic hub on the Caspian Sea.
  • 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_69a8871289048190b00b0d7744b7b2b1 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3f275408190affa93f8cb6a8184 completed March 7, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbdb5d7c8190ab3e7c368041c641 completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:36 p.m.