Triple
T685545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochnia Royal Salt Mine |
E13275
|
entity |
| Predicate | languageOfOfficialGuides |
P17538
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Bochnia Royal Salt Mine, languageOfOfficialGuides, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOfficialGuides Context triple: [Bochnia Royal Salt Mine, languageOfOfficialGuides, Polish]
-
A.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
B.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
C.
languageOfOfficialWebsite
Indicates the language in which an entity’s official website is primarily written or presented.
-
D.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
E.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.