Triple
T3209877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lublin–Brest Offensive |
E67252
|
entity |
| Predicate | frontlineShift |
P10772
|
FINISHED |
| Object | German forces pushed westward |
—
|
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: German forces pushed westward | Statement: [Lublin–Brest Offensive, frontlineShift, German forces pushed westward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontlineShift Context triple: [Lublin–Brest Offensive, frontlineShift, German forces pushed westward]
-
A.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
B.
frontLineChange
chosen
Indicates a change in the position or configuration of the primary boundary or leading edge between opposing sides.
-
C.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
D.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
E.
mainFrontlinePeriod
Indicates the time span during which an entity served as the primary or most active presence on the frontline.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab701c48190b91404ab416f7ce3 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.