Triple

T9218900
Position Surface form Disambiguated ID Type / Status
Subject Douve River valley E221309 entity
Predicate wasStrategicLocationFor P2850 FINISHED
Object Allied forces 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: Allied forces | Statement: [Douve River valley, wasStrategicLocationFor, Allied forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasStrategicLocationFor
Context triple: [Douve River valley, wasStrategicLocationFor, Allied forces]
  • A. strategicLocation chosen
    Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
  • B. wasCitadelOf
    Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
  • C. capturedPlace
    Indicates that an agent took control of or seized a specific place, typically through force or strategic action.
  • D. isStrategicAssetOf
    Indicates that one entity is considered a strategically important resource or capability for another entity, contributing significantly to its long-term goals or competitive advantage.
  • E. placeOfMainEngagement
    Indicates the primary location where an entity carries out its main activities, operations, or engagements.
  • 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_69ca83eae42c8190a0ea9e040710a277 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccda730f688190b64b2cc8c4898ac3 completed April 1, 2026, 8:42 a.m.
PD Predicate disambiguation batch_69cc660ce23c81909c7bbe10f4a05f36 completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:27 p.m.