Triple
T3668136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sopot |
E77811
|
entity |
| Predicate | partOf |
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: [Sopot, partOf, Tricity]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tricity Context triple: [Sopot, partOf, Tricity]
-
A.
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.
-
B.
Warsaw metropolitan area
The Warsaw metropolitan area is the large urban agglomeration centered on Poland’s capital city, encompassing Warsaw and its surrounding suburban and commuter zones.
-
C.
Piła
Piła is a city in northwestern Poland known as a regional economic and transport center in the Greater Poland Voivodeship.
-
D.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
E.
Lublin
Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42997d88190bc765559bd7645fc |
completed | March 8, 2026, 6:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4f021fe148190af7ba4b36caa0ce2 |
completed | March 14, 2026, 5:20 a.m. |
Created at: March 8, 2026, 3:25 p.m.