Triple
T33695640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Climb area of Mount Adams |
E863299
|
entity |
| Predicate | hasPrimarySurfaceType |
P40183
|
FINISHED |
| Object | snow and volcanic rock |
—
|
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: snow and volcanic rock | Statement: [South Climb area of Mount Adams, hasPrimarySurfaceType, snow and volcanic rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySurfaceType Context triple: [South Climb area of Mount Adams, hasPrimarySurfaceType, snow and volcanic rock]
-
A.
hasPrimarySurface
chosen
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasSurfacePreference
Indicates that an entity tends to favor or is best suited for interacting with a particular type of surface over others.
-
C.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
D.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
-
E.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01bdacb52481909c56b0398106640e |
completed | May 11, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a01bd30c8ec8190b1e54d7658b01a8d |
completed | May 11, 2026, 11:27 a.m. |
Created at: May 1, 2026, 1:43 a.m.