Triple
T5006969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decorah crater |
E112519
|
entity |
| Predicate | impactOrigin |
P60799
|
FINISHED |
| Object | meteorite |
—
|
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: meteorite | Statement: [Decorah crater, impactOrigin, meteorite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOrigin Context triple: [Decorah crater, impactOrigin, meteorite]
-
A.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
B.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
C.
impactCategory
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
D.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
-
E.
impactRegion
Indicates the geographic or spatial area that is affected or influenced by a particular event, action, or phenomenon.
- 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.