Triple
T25664589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vilenica Cave |
E643475
|
entity |
| Predicate | hasCaveSystemType |
P57947
|
FINISHED |
| Object | horizontal cave passages |
—
|
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: horizontal cave passages | Statement: [Vilenica Cave, hasCaveSystemType, horizontal cave passages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaveSystemType Context triple: [Vilenica Cave, hasCaveSystemType, horizontal cave passages]
-
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.
isInCavernSystem
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
-
D.
hasCanyonType
Indicates that an entity is characterized by, or classified as having, a specific type or category of canyon.
-
E.
isShowCave
Indicates that a cave or cavern is being displayed, revealed, or made visible within a given context or environment.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 7 p.m.