Triple

T4777120
Position Surface form Disambiguated ID Type / Status
Subject Szare Szeregi E106077 entity
Predicate hadSubdivision P747 FINISHED
Object Zawisza E242811 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: Zawisza | Statement: [Szare Szeregi, hadSubdivision, Zawisza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zawisza
Context triple: [Szare Szeregi, hadSubdivision, Zawisza]
  • A. Zawisza chosen
    Zawisza is a Polish surname historically associated with several notable figures, including nobles, politicians, and cultural personalities.
  • B. Jan Szczepański
    Jan Szczepański was a Polish mountaineer known for participating in pioneering high-altitude ascents in the Andes.
  • C. Piotr z Goniądza
    Piotr z Goniądza was a 16th-century Polish theologian and radical Reformation thinker known for his anti-Trinitarian views and influential role in the early development of the Polish Brethren movement.
  • D. Tadeusz
    Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
  • E. Jędrzej
    Jędrzej is a Polish male given name, traditionally used as a regional or archaic form of the name Andrzej (Andrew).
  • 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_69bd43f3074c8190937e7b0a457fe9f1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd65881e2c8190aa5b57759885b2bb completed March 20, 2026, 3:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69be43caec588190880c47f11d3f2daf completed March 21, 2026, 7:07 a.m.
Created at: March 20, 2026, 1:21 p.m.