Triple
T7003443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gdynia |
E162391
|
entity |
| Predicate | statusOfCityAfterBattle |
P8502
|
FINISHED |
| Object | under Soviet and Polish control |
—
|
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: under Soviet and Polish control | Statement: [Battle of Gdynia, statusOfCityAfterBattle, under Soviet and Polish control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfCityAfterBattle Context triple: [Battle of Gdynia, statusOfCityAfterBattle, under Soviet and Polish control]
-
A.
cityRebuiltAfter
Indicates that a city was reconstructed or significantly restored following a prior event of destruction or severe damage.
-
B.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
-
C.
mainCityDestroyed
Indicates that the primary or central city associated with an entity has been destroyed.
-
D.
destroyedCity
Indicates that an entity has caused the complete or near-complete destruction of a city.
-
E.
conqueredCity
chosen
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc12af788190b3d06ffc46568410 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.