Triple

T15678427
Position Surface form Disambiguated ID Type / Status
Subject Lutakko E377505 entity
Predicate contains P35 FINISHED
Object Lutakko Harbour area E377503 NE 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: Lutakko Harbour area | Statement: [Lutakko, contains, Lutakko Harbour area]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lutakko Harbour area
Context triple: [Lutakko, contains, Lutakko Harbour area]
  • A. Lutakko harbour chosen
    Lutakko harbour is a lakeside port area in Jyväskylä, Finland, known for its marina, events, and recreational waterfront.
  • B. Paljassaare Harbour
    Paljassaare Harbour is a smaller cargo and industrial port area in Tallinn, Estonia, primarily handling bulk and mixed goods within the Port of Tallinn complex.
  • C. Vuosaari Harbour
    Vuosaari Harbour is a major cargo and logistics port area in eastern Helsinki, Finland, serving as the city’s primary freight hub.
  • D. Grandi harbor area
    Grandi harbor area is a revitalized waterfront district in Reykjavík known for its mix of working harbor, cultural venues, restaurants, and creative industries.
  • E. Avarua Harbour
    Avarua Harbour is the main coastal port and anchorage serving the town of Avarua on Rarotonga in the Cook Islands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f2f1640819086efd5a73bb9734a completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6ee0446881909e9c2504d51d49a3 completed May 9, 2026, 5:29 p.m.
Created at: April 10, 2026, 4:16 a.m.