Triple
T685535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochnia Royal Salt Mine |
E13275
|
entity |
| Predicate | hasExhibitionsOn |
P4908
|
FINISHED |
| Object | history of salt mining |
—
|
LITERAL 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: history of salt mining | Statement: [Bochnia Royal Salt Mine, hasExhibitionsOn, history of salt mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionsOn Context triple: [Bochnia Royal Salt Mine, hasExhibitionsOn, history of salt mining]
-
A.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
B.
hasExhibits
chosen
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
C.
hasExhibitionArea
Indicates that an entity includes or provides a designated space or area for exhibitions or displays.
-
D.
hasInteractiveExhibits
Indicates that something contains exhibits designed for active participation or engagement by the audience.
-
E.
exhibitsWorkOf
Indicates that one entity displays or presents the creative works produced by another entity.
- F. None of above.
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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0924dec8190bbbd2bb244f85211 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.