Triple
T18521661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steinheim meteorite crater |
E452596
|
entity |
| Predicate | postImpactEnvironment |
P33269
|
FINISHED |
| Object | crater lake |
—
|
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: crater lake | Statement: [Steinheim meteorite crater, postImpactEnvironment, crater lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postImpactEnvironment Context triple: [Steinheim meteorite crater, postImpactEnvironment, crater lake]
-
A.
hasEnvironmentalImpactOn
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
-
B.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
C.
hasEnvironmentalImpactType
Indicates that something affects the environment in a specific way categorized by a particular type of impact.
-
D.
environmentalImpactGoal
Indicates a goal or target set to influence, reduce, or manage the environmental impact associated with an entity or activity.
-
E.
environmentalOutcome
chosen
Indicates the resulting impact or consequence that an action, event, or condition has on the environment.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338e6e188190a41a4ee12c1ad330 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.