Triple
T5021420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashubia |
E112858
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Lębork |
E284885
|
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: Lębork | Statement: [Kashubia, hasMajorTown, Lębork]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lębork Context triple: [Kashubia, hasMajorTown, Lębork]
-
A.
Lębork
chosen
Lębork is a historic town in northern Poland known for its medieval architecture and location near the Baltic coast.
-
B.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
-
C.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Bartoszyce
Bartoszyce is a town in northern Poland known for its historical architecture and location near the border with Russia’s Kaliningrad Oblast.
-
E.
Racibórz
Racibórz is a historic town in southern Poland, located in the Silesian region near the Czech border, known for its medieval heritage and industrial traditions.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73656edc8190b802ad38d9552b58 |
completed | March 20, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74208348c819080d1b4432ff617c0 |
completed | March 28, 2026, 2:50 a.m. |
Created at: March 20, 2026, 1:36 p.m.