Triple

T19961188
Position Surface form Disambiguated ID Type / Status
Subject Gdańsk Główny E479817 entity
Predicate locatedIn P40 FINISHED
Object Tricity E374064 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: Tricity | Statement: [Gdańsk Główny, locatedIn, Tricity]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tricity
Context triple: [Gdańsk Główny, locatedIn, Tricity]
  • A. Tricity
    Tricity is the urban conglomeration in northern India comprising Chandigarh and its adjoining cities of Mohali and Panchkula.
  • B. Tricity metropolitan area chosen
    The Tricity metropolitan area is an urban region in northern Poland comprising the closely linked Baltic Sea port cities of Gdańsk, Gdynia, and Sopot.
  • C. 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.
  • D. Nowe Miasto
    Nowe Miasto is a village and administrative seat of its own gmina in the Masovian Voivodeship of east-central Poland.
  • E. Warsaw micropolitan area
    The Warsaw micropolitan area is a small urban region centered on Warsaw, Indiana, that serves as a local hub for commerce, services, and surrounding rural communities.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65af4520c81909986a47289ba801e completed April 20, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a07fdccdf408190b0d1130b82e9bfb2 completed May 16, 2026, 5:17 a.m.
Created at: April 10, 2026, 1:54 p.m.