Triple

T3796262
Position Surface form Disambiguated ID Type / Status
Subject Wieliczka and Bochnia Royal Salt Mines E89776 entity
Predicate undergroundLevels P15152 FINISHED
Object multiple mining levels 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: multiple mining levels | Statement: [Wieliczka and Bochnia Royal Salt Mines, undergroundLevels, multiple mining levels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: undergroundLevels
Context triple: [Wieliczka and Bochnia Royal Salt Mines, undergroundLevels, multiple mining levels]
  • A. hasUndergroundDepth
    Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
  • B. undergroundBranch
    Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
  • C. hasUndergroundSection chosen
    Indicates that an entity includes a portion or segment that is located below ground level.
  • D. numberOfBasementLevels
    Indicates the total count of basement levels associated with a given structure or property.
  • E. hasUndergroundConnections
    Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeecefa3608190a7a20ed6df6a64b2 completed March 9, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69aee743c8d08190a9f9c97b836bd703 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:15 p.m.