Triple
T4550393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rickwood Caverns State Park |
E110147
|
entity |
| Predicate | caveType |
P57947
|
FINISHED |
| Object | limestone solution 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: limestone solution cave | Statement: [Rickwood Caverns State Park, caveType, limestone solution cave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caveType Context triple: [Rickwood Caverns State Park, caveType, limestone solution cave]
-
A.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
B.
cavesUsedFor
Indicates that certain caves are utilized for a particular purpose, activity, or function by an entity.
-
C.
hasSpeleothems
Indicates that a cave or subterranean space contains speleothems (mineral formations such as stalactites, stalagmites, or similar deposits).
-
D.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
E.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f5a0a081909977ccbb8aba633c |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:05 p.m.