Triple
T33922672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mine |
E869655
|
entity |
| Predicate | isKarstArea |
P129309
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mine, isKarstArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKarstArea Context triple: [Mine, isKarstArea, true]
-
A.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
B.
karstFeature
chosen
Indicates a relationship where a geographic entity is identified as, or associated with, a karst-related landform or feature formed by the dissolution of soluble rocks.
-
C.
hasKarstTowerFormations
Indicates that the subject possesses or contains karst tower landforms, typically steep or vertical limestone pillars formed by dissolution and erosion.
-
D.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
-
E.
isNaturalFeature
Indicates that the subject is a naturally occurring physical feature of the environment, not created or significantly altered by human activity.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.