Triple
T9084436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman Crater |
E217713
|
entity |
| Predicate | hazardRelatedTo |
P16293
|
FINISHED |
| Object | potential phreatic explosions |
—
|
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: potential phreatic explosions | Statement: [Sherman Crater, hazardRelatedTo, potential phreatic explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardRelatedTo Context triple: [Sherman Crater, hazardRelatedTo, potential phreatic explosions]
-
A.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
C.
hazardManagementConcern
Indicates a relationship where one entity is a source, subject, or focus of concern regarding the identification, assessment, or control of hazards by another entity.
-
D.
hasNotableHazard
chosen
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
safetyRelevant
Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960b45fc8190adf4bdc41b103e86 |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.