Triple

T432144
Position Surface form Disambiguated ID Type / Status
Subject Sea of Azov E9735 entity
Predicate hasStrategicFeature P11759 FINISHED
Object access route to Black Sea 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 route to Black Sea | Statement: [Sea of Azov, hasStrategicFeature, access route to Black Sea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStrategicFeature
Context triple: [Sea of Azov, hasStrategicFeature, access route to Black Sea]
  • A. strategicLocation
    Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
  • B. hasStrategicStrait chosen
    Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
  • C. hasArchitecturalFeature
    Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
  • D. hasUrbanFeature
    Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
  • E. isFortifiedCity
    Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eef07e748190b05392778f3de980 completed Feb. 28, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69a2edd9264c8190b92f9a50348e5541 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.