Triple
T25091260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kłodawa |
E628461
|
entity |
| Predicate | saltMineDepth |
P43725
|
FINISHED |
| Object | over 600 meters |
—
|
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: over 600 meters | Statement: [Kłodawa, saltMineDepth, over 600 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saltMineDepth Context triple: [Kłodawa, saltMineDepth, over 600 meters]
-
A.
saltMineType
Indicates the specific kind or classification of a salt mine associated with an entity.
-
B.
hasUndergroundDepth
chosen
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
D.
depthInRock
Indicates the vertical distance or thickness of material that an object or feature extends into or is embedded within rock.
-
E.
mineLevel
Indicates the depth or richness of mining activity or resources associated with an 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461eabb7c81909cfa0d5db8daca43 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:24 a.m.