Triple
T848058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Group North |
E18320
|
entity |
| Predicate | directionOfAdvance |
P13445
|
FINISHED |
| Object | Northern sector of Eastern Front |
—
|
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: Northern sector of Eastern Front | Statement: [Army Group North, directionOfAdvance, Northern sector of Eastern Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfAdvance Context triple: [Army Group North, directionOfAdvance, Northern sector of Eastern Front]
-
A.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
B.
frontLineDirection
chosen
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
-
C.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
D.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
E.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1e41748190a21cd1ce5ebcb8ff |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.