Triple
T16060831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of St Kinga |
E389604
|
entity |
| Predicate | mineLevel |
P121471
|
FINISHED |
| Object | third level of Wieliczka Salt Mine |
—
|
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: third level of Wieliczka Salt Mine | Statement: [Chapel of St Kinga, mineLevel, third level of Wieliczka Salt Mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineLevel Context triple: [Chapel of St Kinga, mineLevel, third level of Wieliczka Salt Mine]
-
A.
mineName
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
B.
mineLayer
Indicates that an entity is responsible for placing or deploying mines in an area or along a route.
-
C.
mines
Indicates that an agent extracts or removes natural resources or minerals from the ground.
-
D.
mineLocation
Indicates that a specified location is the site where a particular mine (e.g., resource extraction or explosive device) is situated.
-
E.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:57 a.m.