Triple
T25570798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic tundra |
E640966
|
entity |
| Predicate | permafrostDepth |
P158653
|
FINISHED |
| Object | up to hundreds of meters |
—
|
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: up to hundreds of meters | Statement: [Arctic tundra, permafrostDepth, up to hundreds of meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permafrostDepth Context triple: [Arctic tundra, permafrostDepth, up to hundreds of meters]
-
A.
hasPermafrost
Indicates that a location or area contains ground that remains continuously frozen (permafrost) for an extended period.
-
B.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
-
C.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
-
D.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
E.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8ffb11c8190add0643923c6eaf8 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 3:57 p.m.