Triple
T165589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Cave |
E3007
|
entity |
| Predicate | geologicalFormationType |
P4015
|
FINISHED |
| Object | marble cavern |
—
|
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: marble cavern | Statement: [Crystal Cave, geologicalFormationType, marble cavern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalFormationType Context triple: [Crystal Cave, geologicalFormationType, marble cavern]
-
A.
geologicalFormation
chosen
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
E.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.