Triple

T4172211
Position Surface form Disambiguated ID Type / Status
Subject Battle of Lake Ladoga in World War II E86388 entity
Predicate sovietObjective P37592 FINISHED
Object keep Lake Ladoga supply lines open 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: keep Lake Ladoga supply lines open | Statement: [Battle of Lake Ladoga in World War II, sovietObjective, keep Lake Ladoga supply lines open]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sovietObjective
Context triple: [Battle of Lake Ladoga in World War II, sovietObjective, keep Lake Ladoga supply lines open]
  • A. SovietObjective chosen
    Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
  • B. SovietAction
    Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
  • C. RussianObjective
    Indicates that an entity has an objective, goal, or target specifically related to Russia (e.g., Russian interests, territory, institutions, or actors).
  • D. SovietOperation
    Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
  • E. involvedUnitSoviet
    Indicates that a Soviet military or organizational unit was involved in a particular event, operation, or action.
  • 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02c9e12c81908d0b22671fea2453 completed March 9, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69af018fb0948190a9701b2e8e5d9bac completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:45 p.m.