Triple
T3586332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Strategic Offensive Operation |
E75917
|
entity |
| Predicate | pushedBackDistance |
P41489
|
FINISHED |
| Object | 100–250 kilometers from Moscow |
—
|
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: 100–250 kilometers from Moscow | Statement: [Moscow Strategic Offensive Operation, pushedBackDistance, 100–250 kilometers from Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pushedBackDistance Context triple: [Moscow Strategic Offensive Operation, pushedBackDistance, 100–250 kilometers from Moscow]
-
A.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
B.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
C.
wentToDistance
chosen
Indicates that an entity traveled to or reached a specified distance from a reference point.
-
D.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
E.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc137eb708190809cd52b6deb227c |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.