Triple
T15496603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacitan Regency |
E378832
|
entity |
| Predicate | hasNaturalCaveType |
P57947
|
FINISHED |
| Object | limestone caves |
—
|
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: limestone caves | Statement: [Pacitan Regency, hasNaturalCaveType, limestone caves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalCaveType Context triple: [Pacitan Regency, hasNaturalCaveType, limestone caves]
-
A.
caveType
chosen
Indicates the specific classification or kind of cave associated with an entity.
-
B.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
C.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
D.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
E.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faecd60819091eeaa56c9c8f67d |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:52 a.m.