Triple
T5006970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decorah crater |
E112519
|
entity |
| Predicate | impactTargetRock |
P60800
|
FINISHED |
| Object | sedimentary rocks |
—
|
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: sedimentary rocks | Statement: [Decorah crater, impactTargetRock, sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactTargetRock Context triple: [Decorah crater, impactTargetRock, sedimentary rocks]
-
A.
identifiedAsImpactStructure
Indicates that something has been determined or classified as an impact structure, typically formed by the collision of an extraterrestrial body with a planetary surface.
-
B.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
C.
centralRockName
Indicates that an entity has a specific name assigned to its central rock or primary rock feature.
-
D.
impactTower
Indicates that one entity exerts a significant force or collision upon a tower-like structure, affecting its state or stability.
-
E.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
- F. None of above. chosen
Provenance (4 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:35 p.m.