Triple
T685520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochnia Royal Salt Mine |
E13275
|
entity |
| Predicate | hasUndergroundChapels |
P15152
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bochnia Royal Salt Mine, hasUndergroundChapels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundChapels Context triple: [Bochnia Royal Salt Mine, hasUndergroundChapels, yes]
-
A.
hasChapelCountApprox
Indicates an approximate number of chapels associated with an entity.
-
B.
hasUndergroundSection
chosen
Indicates that an entity includes a portion or segment that is located below ground level.
-
C.
hasCathedralChapter
Indicates that an ecclesiastical jurisdiction or church possesses or is served by a cathedral chapter as its governing or advisory body.
-
D.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
E.
hasCoCathedral
Indicates that a primary cathedral is associated with an additional church that shares its status and functions as a co-cathedral within the same diocese or ecclesiastical jurisdiction.
- 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.