Triple
T32195467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plac Bankowy |
E822391
|
entity |
| Predicate | wasSignificantlyDamagedDuring |
P992
|
FINISHED |
| Object | World War II |
—
|
NE NERFINISHED |
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: World War II | Statement: [Plac Bankowy, wasSignificantlyDamagedDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSignificantlyDamagedDuring Context triple: [Plac Bankowy, wasSignificantlyDamagedDuring, World War II]
-
A.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
B.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
damagedIn
chosen
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
D.
notableLocationOfDamage
Indicates the specific place where damage is prominently present or has significantly occurred.
-
E.
wasBombardedDuring
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb3795fc8190bfcb00d45aa887a1 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.