Triple

T37638188
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Sztumska Wieś E936544 entity
Predicate limitedSwedishNavalPresenceIn P189084 FINISHED
Object Baltic Sea NE NERFINISHED

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: Baltic Sea | Statement: [Treaty of Sztumska Wieś, limitedSwedishNavalPresenceIn, Baltic Sea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedSwedishNavalPresenceIn
Context triple: [Treaty of Sztumska Wieś, limitedSwedishNavalPresenceIn, Baltic Sea]
  • A. fleetStrengthSwedish
    Indicates the relative naval or fleet power possessed by the Swedish side in a given context or scenario.
  • B. limitedTorpedoBoatsTo
    Indicates that an entity imposes a restriction on the number or capabilities of torpedo boats available to another entity or within a specified context.
  • C. SwedishTacticalAdvantage
    Indicates that Sweden holds a superior strategic or tactical position over another party in a given context or conflict.
  • D. restrictedNavalRightsInCaspianFor
    Indicates that the entity has limited or constrained rights to conduct naval activities in the Caspian Sea.
  • E. navalOpposition
    Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
  • F. None of above. chosen

Provenance (4 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_69f76ed31d8881908405da6c6d2f0463 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
PDg Predicate description generation batch_69fbb083ab708190a18b045311106f27 completed May 6, 2026, 9:20 p.m.
Created at: May 3, 2026, 4:18 p.m.