Triple

T20895964
Position Surface form Disambiguated ID Type / Status
Subject Borsuk infantry fighting vehicle E514534 entity
Predicate originLanguageName P3048 FINISHED
Object Borsuk 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: Borsuk | Statement: [Borsuk infantry fighting vehicle, originLanguageName, Borsuk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borsuk
Context triple: [Borsuk infantry fighting vehicle, originLanguageName, Borsuk]
  • A. Borsuk chosen
    Borsuk is a Polish surname most notably associated with mathematician Karol Borsuk, known for his contributions to topology.
  • B. Bielecki
    Bielecki is a Polish surname borne by various notable individuals across fields such as politics, sports, and mountaineering.
  • C. Arciszewski
    Arciszewski is a Polish surname most notably borne by Tomasz Arciszewski, a socialist politician and Prime Minister of the Polish government-in-exile during World War II.
  • D. Borówek
    Borówek is a small village in central Poland located within the administrative district of Gmina Bielawy.
  • E. Morawka
    Morawka is a river in southwestern Poland that serves as a tributary of the Nysa Kłodzka.
  • 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_69e0b4f7ebe48190952a85547a0f31a1 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6d06233588190942493b709e30820 completed April 21, 2026, 1:18 a.m.
Created at: April 16, 2026, 12:47 p.m.