Triple
T7003442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gdynia |
E162391
|
entity |
| Predicate | statusOfCityBeforeBattle |
P73538
|
FINISHED |
| Object | under German occupation |
—
|
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 German occupation | Statement: [Battle of Gdynia, statusOfCityBeforeBattle, under German occupation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfCityBeforeBattle Context triple: [Battle of Gdynia, statusOfCityBeforeBattle, under German occupation]
-
A.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
-
B.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
C.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
D.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
E.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.