Triple
T2134083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1970 Polish protests |
E46609
|
entity |
| Predicate | significantPlace |
P1098
|
FINISHED |
| Object | Słupsk |
E178809
|
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: Słupsk | Statement: [1970 Polish protests, significantPlace, Słupsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Słupsk Context triple: [1970 Polish protests, significantPlace, Słupsk]
-
A.
Słupsk
chosen
Słupsk is a historic city in northern Poland known for its medieval architecture and location near the Baltic Sea.
-
B.
Koszalin
Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
-
C.
Giżycko
Giżycko is a popular lakeside town in northeastern Poland, known as a major sailing and tourism center in the Masurian Lake District.
-
D.
Olsztyn
Olsztyn is a historic city in northern Poland known for its medieval architecture, lakes, and role as the capital of the Warmian-Masurian Voivodeship.
-
E.
Kościerzyna
Kościerzyna is a historic town in northern Poland known as a local cultural and economic center within the Kashubian region.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b54c0e702081909384b804fb1ade90 |
completed | March 14, 2026, 11:52 a.m. |
Created at: March 4, 2026, 7:44 p.m.