Triple

T21285729
Position Surface form Disambiguated ID Type / Status
Subject Port of Kotka E524652 entity
Predicate hasNearbyCity P350 FINISHED
Object Hamina 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: Hamina | Statement: [Port of Kotka, hasNearbyCity, Hamina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hamina
Context triple: [Port of Kotka, hasNearbyCity, Hamina]
  • A. Hamina chosen
    Hamina is a coastal town and municipality in southeastern Finland known for its historic star-shaped fortress and strategic location on the Gulf of Finland.
  • B. Ghadamisi
    Ghadamisi is an alternative name for the Ghadamès Berber language spoken in and around the oasis town of Ghadamès in western Libya.
  • C. Aïn El Hammam
    Aïn El Hammam is a town in northern Algeria known for its mountainous Kabylie setting and Berber cultural heritage.
  • D. Ajdabiya
    Ajdabiya is a strategic town in northeastern Libya that became a key battleground during the 2011 Libyan Civil War due to its location on major coastal and desert routes.
  • E. Al Azaiba
    Al Azaiba is a coastal residential and commercial district in Muscat, Oman, known for its beach, proximity to the airport, and growing urban development.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5171f6c8190a5d57201ede73811 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d658e08190ad2f267123d53ede completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:03 p.m.