Triple

T4777123
Position Surface form Disambiguated ID Type / Status
Subject Szare Szeregi E106077 entity
Predicate ZawiszaRole P59256 FINISHED
Object younger scouts for auxiliary and communication tasks LITERAL 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: younger scouts for auxiliary and communication tasks | Statement: [Szare Szeregi, ZawiszaRole, younger scouts for auxiliary and communication tasks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ZawiszaRole
Context triple: [Szare Szeregi, ZawiszaRole, younger scouts for auxiliary and communication tasks]
  • A. PolishCommander
    Indicates that an entity serves as a military commander associated with Poland.
  • B. successorInSandomierz
    Indicates that one entity directly follows another as its successor in the context of Sandomierz (e.g., in an office, role, or position associated with Sandomierz).
  • C. PrussianCommander
    Indicates that an individual holds the position or role of a commander within the Prussian military forces.
  • D. notableBattleRole
    Indicates the specific role or function an entity played in a notable or historically significant battle.
  • E. MongolianCommander
    Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
  • F. None of above. chosen

Provenance (4 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_69bd69237f80819090713ed62653fb75 completed March 20, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69bd622be1388190ab5511b589c878c0 completed March 20, 2026, 3:05 p.m.
PDg Predicate description generation batch_69bd6922407481908565ed0b1dac2b30 completed March 20, 2026, 3:34 p.m.
Created at: March 20, 2026, 1:21 p.m.