Triple
T12339725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łeba |
E294188
|
entity |
| Predicate | hasMouthNear |
P350
|
FINISHED |
| Object | Łeba (town) |
E294188
|
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: Łeba (town) | Statement: [Łeba, hasMouthNear, Łeba (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łeba (town) Context triple: [Łeba, hasMouthNear, Łeba (town)]
-
A.
Łeba
chosen
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
B.
Lębork
Lębork is a historic town in northern Poland known for its medieval architecture and location near the Baltic coast.
-
C.
Lubień
Lubień is a village in southern Poland, known here as the place where prominent historian and politician Bronisław Geremek died.
-
D.
Łęczna
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
-
E.
Lubliniec
Lubliniec is a historic town in southern Poland’s Silesian Voivodeship, known for its medieval origins, regional cultural heritage, and surrounding forested landscapes.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7758dc8190bbc6a9ad00b01dce |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62aa7e33c819084e5673a5fb8cac7 |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:53 p.m.