Triple

T20506972
Position Surface form Disambiguated ID Type / Status
Subject Edwinton E503459 entity
Predicate formerNameOf P65 FINISHED
Object Bismarck NE NERFINISHED

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: Bismarck | Statement: [Edwinton, formerNameOf, Bismarck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bismarck
Context triple: [Edwinton, formerNameOf, Bismarck]
  • A. Bismarck
    Bismarck was a famous German World War II battleship renowned for its powerful armament, heavy armor, and dramatic sinking after a major North Atlantic pursuit.
  • B. Bismarck chosen
    Bismarck is a mid-sized city in south-central North Dakota that serves as the state’s political and administrative center.
  • C. Prince of Bismarck
    Prince of Bismarck is a hereditary noble title in the German aristocracy historically associated with the statesman Otto von Bismarck and his descendants.
  • D. Dukenburg
    Dukenburg is a residential district in the southwest of Nijmegen in the Netherlands, known for its post-war urban planning and local railway connectivity.
  • E. Tirpitz
    Tirpitz was a German World War II battleship, sister ship to Bismarck, known for its powerful presence in Norwegian waters and the significant Allied efforts devoted to neutralizing it.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69dc82dd0819085d64d65a1e72c70 completed April 20, 2026, 9:42 p.m.
Created at: April 16, 2026, 11:36 a.m.