Triple

T3472572
Position Surface form Disambiguated ID Type / Status
Subject Walcheren E73296 entity
Predicate wasStrategicFor P5437 FINISHED
Object access to port of Antwerp 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: access to port of Antwerp | Statement: [Walcheren, wasStrategicFor, access to port of Antwerp]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasStrategicFor
Context triple: [Walcheren, wasStrategicFor, access to port of Antwerp]
  • A. hasStrategicFunction
    Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
  • B. strategicEffectOfVictory
    Indicates that a victory produces a broader strategic impact or consequence beyond the immediate outcome of the conflict or contest.
  • C. hasStrategicPass
    Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
  • D. goalDuringWar
    Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
  • E. strategicGoal chosen
    Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
  • 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_69ad85b2fed48190948c8765e453d270 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb3cc8488190b97c732e3f600a90 completed March 8, 2026, 6:09 p.m.
PD Predicate disambiguation batch_69adae07802c8190919c49b0e65b2797 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:17 p.m.