Triple
T32780857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Space Cavern |
E838350
|
entity |
| Predicate | isCommercialCave |
P179855
|
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: [Inner Space Cavern, isCommercialCave, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialCave Context triple: [Inner Space Cavern, isCommercialCave, true]
-
A.
isShowCave
Indicates that a cave or cavern is being displayed, revealed, or made visible within a given context or environment.
-
B.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
C.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
caveType
Indicates the specific classification or kind of cave associated with an entity.
-
E.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:14 a.m.