Triple
T28325958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowlitz Cleaver |
E717407
|
entity |
| Predicate | isFeatureTypeOnMountRainier |
P88540
|
FINISHED |
| Object | cleaver |
—
|
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: cleaver | Statement: [Cowlitz Cleaver, isFeatureTypeOnMountRainier, cleaver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFeatureTypeOnMountRainier Context triple: [Cowlitz Cleaver, isFeatureTypeOnMountRainier, cleaver]
-
A.
isNaturalFeature
Indicates that the subject is a naturally occurring physical feature of the environment, not created or significantly altered by human activity.
-
B.
mountainFeature
chosen
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
C.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
D.
hasMoraineType
Indicates the specific type or classification of moraine associated with a given glacial or geomorphological feature.
-
E.
isRockySummitOf
Indicates that one entity is the rocky summit or peak portion of another, typically higher-level, geographic feature.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492f24008190a122ed65e12feffa |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:28 a.m.