Triple
T35040679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kow-Ata cave |
E1011060
|
entity |
| Predicate | hasSubterraneanLake |
P123528
|
FINISHED |
| Object | Kow-Ata underground lake |
—
|
NE NERFINISHED |
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: Kow-Ata underground lake | Statement: [Kow-Ata cave, hasSubterraneanLake, Kow-Ata underground lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubterraneanLake Context triple: [Kow-Ata cave, hasSubterraneanLake, Kow-Ata underground lake]
-
A.
hasSubglacialLake
Indicates that a glacier or ice sheet contains a lake of liquid water located beneath its ice.
-
B.
hasVolcanicLake
Indicates that an entity contains or features a lake formed in or directly associated with volcanic activity.
-
C.
hasSubglacialEnvironment
Indicates that something possesses or is associated with an environment located beneath a glacier or ice sheet.
-
D.
hasHydrocarbonLakes
Indicates that the subject possesses or contains lakes composed primarily of liquid hydrocarbons rather than water.
-
E.
hasLakes
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:01 p.m.