Triple
T12047916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Barbarossa southern sector |
E286833
|
entity |
| Predicate | axisAdvanceDirection |
P56811
|
FINISHED |
| Object | from Poland into Ukraine |
—
|
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 Poland into Ukraine | Statement: [Operation Barbarossa southern sector, axisAdvanceDirection, from Poland into Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axisAdvanceDirection Context triple: [Operation Barbarossa southern sector, axisAdvanceDirection, from Poland into Ukraine]
-
A.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
C.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
D.
transportAxis
chosen
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
E.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.