Triple
T3668171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sopot |
E77811
|
entity |
| Predicate | hasBeach |
P1922
|
FINISHED |
| Object | Sopot Beach |
E77811
|
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: Sopot Beach | Statement: [Sopot, hasBeach, Sopot Beach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sopot Beach Context triple: [Sopot, hasBeach, Sopot Beach]
-
A.
Gdynia Orłowo Beach
Gdynia Orłowo Beach is a scenic sandy shoreline in the Orłowo district of Gdynia, Poland, known for its wooden pier, dramatic cliff views, and picturesque setting on the Baltic coast.
-
B.
Ewa Beach
Ewa Beach is a coastal residential community on the leeward side of Oʻahu in Hawaii, known for its beaches, golf courses, and suburban neighborhoods.
-
C.
Słupsk Coast
Słupsk Coast is a coastal region in northern Poland along the Baltic Sea, known for its sandy beaches, dunes, and seaside resorts.
-
D.
Sopot
chosen
Sopot is a Polish Baltic Sea resort city famous for its sandy beaches, long wooden pier, and vibrant spa and nightlife culture.
-
E.
Sopot
Sopot is a suburban municipality of Belgrade, Serbia, known for its rural character and proximity to the Avala and Kosmaj mountains.
- 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_69b4884e36108190a19887e81921fe32 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:25 p.m.