Triple
T33711955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kłuszyn |
E863764
|
entity |
| Predicate | commanderSidePolishLithuanian |
P23377
|
FINISHED |
| Object | Stanisław Żółkiewski |
E245341
|
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: Stanisław Żółkiewski | Statement: [Battle of Kłuszyn, commanderSidePolishLithuanian, Stanisław Żółkiewski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderSidePolishLithuanian Context triple: [Battle of Kłuszyn, commanderSidePolishLithuanian, Stanisław Żółkiewski]
-
A.
PolishCommander
chosen
Indicates that an entity serves as a military commander associated with Poland.
-
B.
commanderHungarianSide
Indicates that the subject served as a commander on the Hungarian side in a conflict or military engagement.
-
C.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
D.
commanderSideRussia
Indicates that the commander is aligned with, fighting for, or acting on behalf of the Russian side in a conflict or military context.
-
E.
commanderCountry
Indicates that a person serving as a commander is associated with or represents a specific country in that commanding role.
- F. None of above.
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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae3071448190b2fec7c5cf9d5282 |
completed | June 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 1:43 a.m.