Triple
T17481883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimsener Höhle |
E425679
|
entity |
| Predicate | hasKarstType |
P99688
|
FINISHED |
| Object | karst spring cave |
—
|
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: karst spring cave | Statement: [Wimsener Höhle, hasKarstType, karst spring cave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKarstType Context triple: [Wimsener Höhle, hasKarstType, karst spring cave]
-
A.
hasKarstTowerFormations
Indicates that the subject possesses or contains karst tower landforms, typically steep or vertical limestone pillars formed by dissolution and erosion.
-
B.
isKarstCave
chosen
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
C.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
hasSpeleothems
Indicates that a cave or subterranean space contains speleothems (mineral formations such as stalactites, stalagmites, or similar deposits).
-
E.
caveType
Indicates the specific classification or kind of cave 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451c0db14819098922453131fb40a |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.