Triple
T10473251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieluń |
E246981
|
entity |
| Predicate | bombardmentContext |
P34756
|
FINISHED |
| Object | invasion of Poland |
—
|
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: invasion of Poland | Statement: [Wieluń, bombardmentContext, invasion of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombardmentContext Context triple: [Wieluń, bombardmentContext, invasion of Poland]
-
A.
bombardedBy
Indicates that an entity is subjected to an intense or repeated attack, impact, or influx from another entity.
-
B.
wasBombardedDuring
chosen
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
-
C.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
D.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
-
E.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094daac081908e0ba5e10c1bbb67 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.