Triple

T16393756
Position Surface form Disambiguated ID Type / Status
Subject Radmor E398123 entity
Predicate basedIn P40 FINISHED
Object Gdynia, Poland E12134 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: Gdynia, Poland | Statement: [Radmor, basedIn, Gdynia, Poland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gdynia, Poland
Context triple: [Radmor, basedIn, Gdynia, Poland]
  • A. Gdynia chosen
    Gdynia is a major seaport city on Poland’s Baltic coast, developed rapidly in the 20th century into one of the country’s key maritime and economic centers.
  • B. Gdańsk
    Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
  • C. Wrocanka, Poland
    Wrocanka, Poland is a small village in southeastern Poland known as the birthplace of former Polish communist leader Stanisław Kania.
  • D. Tychy, Poland
    Tychy, Poland is an industrial city in the Silesian region known for its major automotive manufacturing plants and brewing industry.
  • E. Gdynia metropolitan area
    The Gdynia metropolitan area is an urban region in northern Poland centered on the port city of Gdynia, forming part of the broader Tricity conurbation on the Baltic Sea.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e326447a7481909feac905edc707ec completed April 18, 2026, 6:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003575e51c8190a8677f658eb73a30 completed May 10, 2026, 7:36 a.m.
Created at: April 10, 2026, 5:08 a.m.