Triple
T19840405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plovdiv Province |
E476709
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Sopot Municipality |
—
|
NE NERFINISHED |
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 Municipality | Statement: [Plovdiv Province, hasMunicipality, Sopot Municipality]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sopot Municipality Context triple: [Plovdiv Province, hasMunicipality, Sopot Municipality]
-
A.
Sopot
Sopot is a suburban municipality of Belgrade, Serbia, known for its rural character and proximity to the Avala and Kosmaj mountains.
-
B.
Sopot
Sopot is a Polish Baltic Sea resort city famous for its sandy beaches, long wooden pier, and vibrant spa and nightlife culture.
-
C.
Sopot
chosen
Sopot is a small Bulgarian town in the Rose Valley, known as the birthplace of national writer Ivan Vazov and for its traditional architecture and cultural heritage.
-
D.
Sopot City Council
Sopot City Council is the elected municipal legislative body responsible for setting local policies, budgets, and regulations for the city of Sopot in Poland.
-
E.
Serock
Serock is a locality situated near the Western Bug River in eastern Europe.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580576748190b85e234b01209ae7 |
completed | April 20, 2026, 4:44 p.m. |
Created at: April 10, 2026, 1:50 p.m.