Triple
T502156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Polish Army |
E10423
|
entity |
| Predicate | garrisonAfterWar |
P14448
|
FINISHED |
| Object | territory of postwar 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: territory of postwar Poland | Statement: [1st Polish Army, garrisonAfterWar, territory of postwar Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonAfterWar Context triple: [1st Polish Army, garrisonAfterWar, territory of postwar Poland]
-
A.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
B.
garrisonDuringBattle
Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
-
C.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
D.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
E.
garrisonLabel
Indicates the designation or identifying label assigned to a military garrison associated with an entity.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.