Triple

T7464425
Position Surface form Disambiguated ID Type / Status
Subject Leer E176336 entity
Predicate hasMaritimeFeature P77269 FINISHED
Object inland port 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: inland port | Statement: [Leer, hasMaritimeFeature, inland port]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMaritimeFeature
Context triple: [Leer, hasMaritimeFeature, inland port]
  • A. containsCoastalFeature
    Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
  • B. hasCoastalCharacteristic
    Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
  • C. hasShoreFeature
    Indicates that a shore or coastline possesses a specific physical or environmental feature.
  • D. hasNotableSea
    Indicates that an entity is associated with or contains a sea that is considered notable or significant.
  • E. hasCoastline
    Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
  • 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_69c69f21632481908bf83f6c6da897e3 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f3d9d25c819087efc772b5b127fa completed March 27, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69c6f03bad9c8190bdd5abb86d37df47 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f386daac81908ded91b397b44148 completed March 27, 2026, 9:15 p.m.
Created at: March 27, 2026, 3:40 p.m.