Triple
T10948948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Armia (Niemcy) |
E258673
|
entity |
| Predicate | odegrałaRolę |
P68592
|
FINISHED |
| Object | kluczowa rola w ataku na Polskę w 1939 roku |
—
|
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: kluczowa rola w ataku na Polskę w 1939 roku | Statement: [10 Armia (Niemcy), odegrałaRolę, kluczowa rola w ataku na Polskę w 1939 roku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odegrałaRolę Context triple: [10 Armia (Niemcy), odegrałaRolę, kluczowa rola w ataku na Polskę w 1939 roku]
-
A.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
B.
playRoleIn
chosen
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
E.
ZawiszaRole
Indicates that an entity holds or is assigned a specific role or function within the Zawisza context.
- F. None of above.
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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ec7028819084f5ce2035a128e4 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.