Triple
T4960240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilibino |
E111386
|
entity |
| Predicate | permafrost |
P15762
|
FINISHED |
| Object | built on continuous permafrost zone |
—
|
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: built on continuous permafrost zone | Statement: [Bilibino, permafrost, built on continuous permafrost zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permafrost Context triple: [Bilibino, permafrost, built on continuous permafrost zone]
-
A.
hasPermafrost
chosen
Indicates that a location or area contains ground that remains continuously frozen (permafrost) for an extended period.
-
B.
cryogen
Indicates that an entity is preserved or maintained at extremely low temperatures, typically to halt biological or chemical processes.
-
C.
isGlaciologicallyRelatedTo
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
-
D.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
E.
snowCover
Indicates that one entity is covered by or blanketed with snow.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.