Triple
T2427246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rymanów |
E53557
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Krosno |
E217525
|
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: Krosno | Statement: [Rymanów, locatedNear, Krosno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krosno Context triple: [Rymanów, locatedNear, Krosno]
-
A.
Krosno
chosen
Krosno is a historic town in southeastern Poland known for its glassmaking industry and well-preserved old town.
-
B.
Kłodzko
Kłodzko is a historic town in southwestern Poland known for its well-preserved medieval architecture and prominent hilltop fortress.
-
C.
Świdnica
Świdnica is a historic town in southwestern Poland known for its well-preserved medieval architecture and the UNESCO-listed Church of Peace.
-
D.
Cieszyn
Cieszyn is a historic town in southern Poland on the Olza River, known for its shared Polish-Czech heritage and well-preserved old town.
-
E.
Tarnów
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc99d0b1c8190bf0a94fa07919d21 |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2e803e994819085dae09224fae2a3 |
completed | March 12, 2026, 4:21 p.m. |
Created at: March 6, 2026, 9:42 p.m.