Triple
T10948955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Armia (Niemcy) |
E258673
|
entity |
| Predicate | rola |
P268
|
FINISHED |
| Object | główne uderzenie na zachodnią Polskę |
—
|
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: główne uderzenie na zachodnią Polskę | Statement: [10 Armia (Niemcy), rola, główne uderzenie na zachodnią Polskę]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rola Context triple: [10 Armia (Niemcy), rola, główne uderzenie na zachodnią Polskę]
-
A.
rollout
Indicates the action of introducing or deploying something (such as a product, feature, or policy) from a limited or initial state to broader or full availability over time.
-
B.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
C.
rom
Indicates a romantic relationship or romantic involvement between the related entities.
-
D.
rukus
Indicates that an entity is associated with or participates in a disturbance, commotion, or noisy disruptive event involving another entity.
-
E.
roundel
Indicates that one entity bears, displays, or is marked with a circular emblem or symbol representing another entity.
- 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.