Triple

T8114349
Position Surface form Disambiguated ID Type / Status
Subject Gdynia Orłowo Beach E189434 entity
Predicate locatedIn P40 FINISHED
Object Orłowo E78629 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: Orłowo | Statement: [Gdynia Orłowo Beach, locatedIn, Orłowo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orłowo
Context triple: [Gdynia Orłowo Beach, locatedIn, Orłowo]
  • A. Orłowo chosen
    Orłowo is a coastal district of Gdynia in northern Poland, known for its scenic cliffs, pier, and Baltic Sea beaches.
  • B. Zułowo
    Zułowo is a village in present-day Lithuania best known as the birthplace of Józef Piłsudski, a key figure in Poland’s struggle for independence.
  • C. Grodkowo
    Grodkowo is a settlement in northern Poland located within the Warmian-Masurian Voivodeship, a region known for its lakes and natural landscapes.
  • D. Działdowo
    Działdowo is a town in northern Poland known for its historical significance and location within the Warmian-Masurian Voivodeship.
  • E. Kozłowo
    Kozłowo is a village in northern Poland that serves as an important local center within the Warmian-Masurian Voivodeship.
  • 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_69ca82baad008190ab2859712b9b1607 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb432f2a24819097be6ab9b03567bd completed March 31, 2026, 3:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69f08ec96fe88190b791e6f50f39173f completed April 28, 2026, 10:41 a.m.
Created at: March 30, 2026, 5:32 p.m.