Triple
T25080041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wetumpka Impact Crater vicinity |
E628159
|
entity |
| Predicate | impactTargetEnvironment |
P57204
|
FINISHED |
| Object | shallow marine shelf |
—
|
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: shallow marine shelf | Statement: [Wetumpka Impact Crater vicinity, impactTargetEnvironment, shallow marine shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactTargetEnvironment Context triple: [Wetumpka Impact Crater vicinity, impactTargetEnvironment, shallow marine shelf]
-
A.
impactExperimentTarget
Indicates that an experiment directly affects, influences, or produces a measurable impact on a specified target.
-
B.
hasEnvironmentalTarget
Indicates that an entity has a specified environmental objective, goal, or target it aims to achieve or comply with.
-
C.
impactScope
Indicates the extent or range within which an action, event, or entity produces effects or consequences.
-
D.
targetsEcosystem
chosen
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
-
E.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:22 a.m.