Triple
T22820177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southeastern Poland |
E565204
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Krosno |
—
|
NE NERFINISHED |
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: [southeastern Poland, majorCity, Krosno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krosno Context triple: [southeastern Poland, majorCity, Krosno]
-
A.
Krosno
chosen
Krosno is a historic town in southeastern Poland known for its glassmaking industry and well-preserved old town.
-
B.
Krosno Odrzańskie
Krosno Odrzańskie is a small historic town in western Poland, located on the Oder River in the Lubusz Voivodeship.
-
C.
Komorno
Komorno is a small settlement that forms one of the administrative parts of the town of Blovice in the Czech Republic.
-
D.
Zloczow
Zloczow is the historical Polish name for the town now known as Zolochiv, located in western Ukraine.
-
E.
Kłodzko
Kłodzko is a historic town in southwestern Poland known for its well-preserved medieval architecture and prominent hilltop fortress.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcf39a88190bec26affc304236d |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:33 p.m.