Triple
T9185779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Guards Army |
E220453
|
entity |
| Predicate | advanceDirection |
P77537
|
FINISHED |
| Object | From central Ukraine into Eastern Europe |
—
|
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: From central Ukraine into Eastern Europe | Statement: [5th Guards Army, advanceDirection, From central Ukraine into Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advanceDirection Context triple: [5th Guards Army, advanceDirection, From central Ukraine into Eastern Europe]
-
A.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
B.
continuesToward
chosen
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
C.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
D.
mayAdvanceTo
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
E.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31a52508190a83ccd76f3aa039b |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.