Triple
T34614575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chubb Crater |
E888827
|
entity |
| Predicate | impactOriginConfirmed |
P185690
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Chubb Crater, impactOriginConfirmed, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOriginConfirmed Context triple: [Chubb Crater, impactOriginConfirmed, 1950s]
-
A.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
B.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
actualImpactSite
Indicates the location where an impact actually occurred, as opposed to a predicted, intended, or nominal impact site.
-
E.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 2:03 a.m.