Triple
T10149592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lądek-Zdrój |
E232595
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Biała Lądecka |
E609845
|
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: Biała Lądecka | Statement: [Lądek-Zdrój, locatedOnRiver, Biała Lądecka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biała Lądecka Context triple: [Lądek-Zdrój, locatedOnRiver, Biała Lądecka]
-
A.
Biała Lądecka
chosen
Biała Lądecka is a river in southwestern Poland that flows through the Kłodzko region before joining the Nysa Kłodzka.
-
B.
Bukowiec
Bukowiec is a village in southwestern Poland known for its scenic location in the Karkonosze foothills and historic park-and-palace complex.
-
C.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
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.
Mława
Mława is a town in north-central Poland known for its historical significance, including a major World War II battle, and its regional cultural and economic role.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec03e80c81909c813dae91c56272 |
completed | April 2, 2026, 4:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e6369c848190984394eedf2f07eb |
completed | April 5, 2026, 10:46 p.m. |
Created at: March 30, 2026, 9:08 p.m.