Triple
T6145334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochnia Regional Museum |
E137060
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Bochnia |
E24511
|
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: Bochnia | Statement: [Bochnia Regional Museum, locatedIn, Bochnia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bochnia Context triple: [Bochnia Regional Museum, locatedIn, Bochnia]
-
A.
Bochnia
chosen
Bochnia is a historic town in southern Poland best known for its medieval salt mine, one of the oldest in Europe.
-
B.
Mszana Dolna
Mszana Dolna is a small town in southern Poland situated in a picturesque valley surrounded by the mountains of the Western Beskids.
-
C.
Kraśnik
Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
-
D.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
-
E.
Bolesławiec
Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdd2dc0819080a4adf0cead3603 |
completed | March 22, 2026, 9:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb135210188190b61482e2d5747783 |
completed | March 31, 2026, 12:20 a.m. |
Created at: March 22, 2026, 4:16 p.m.