Triple
T30883295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lars Christensen Peak |
E786682
|
entity |
| Predicate | hasSummitCover |
P136501
|
FINISHED |
| Object | ice |
—
|
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: ice | Statement: [Lars Christensen Peak, hasSummitCover, ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitCover Context triple: [Lars Christensen Peak, hasSummitCover, ice]
-
A.
hasSummitCoveredBy
chosen
Indicates that the summit or highest point of an entity is physically covered, capped, or overlaid by another material or feature.
-
B.
summitCoveredBy
Indicates that a summit or peak is located within and thus covered by a particular geographic or administrative area.
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
E.
coversSummit
Indicates that one entity extends over, encloses, or forms a protective or obscuring layer around the summit of another entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 29, 2026, 8:48 p.m.