Triple
T7146705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karkonosze |
E166586
|
entity |
| Predicate | nearestCity |
P350
|
FINISHED |
| Object | Jelenia Góra |
E307156
|
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: Jelenia Góra | Statement: [Karkonosze, nearestCity, Jelenia Góra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jelenia Góra Context triple: [Karkonosze, nearestCity, Jelenia Góra]
-
A.
Jelenia Góra
chosen
Jelenia Góra is a historic city in southwestern Poland, known for its picturesque setting in the Karkonosze Mountains and its well-preserved old town architecture.
-
B.
Zielona Góra
Zielona Góra is a city in western Poland known for its wine-making tradition and annual wine festival.
-
C.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
D.
Polkowice
Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
-
E.
Inowrocław
Inowrocław is a historic spa and industrial city in north-central Poland, known for its saltworks and location in the Kuyavia 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d4f3388190941f03fd80b0c223 |
completed | March 27, 2026, 8:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2693f054081909fe58a252bd76226 |
completed | April 5, 2026, 1:53 p.m. |
Created at: March 27, 2026, 2:46 p.m.