Triple
T30036162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalkaska sand |
E763162
|
entity |
| Predicate | erosionHazard |
P106714
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Kalkaska sand, erosionHazard, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionHazard Context triple: [Kalkaska sand, erosionHazard, moderate]
-
A.
erosionRate
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
B.
landslideProne
Indicates that an area or location is susceptible to experiencing landslides under certain conditions.
-
C.
geologicHazardLevel
chosen
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
-
D.
cliffStability
Indicates the degree to which a cliff is structurally secure and resistant to collapse or erosion under current conditions.
-
E.
geologicalHazardZoneFor
Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d44f2081908ffa58a7709907ba |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:51 p.m.