Triple
T24069026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannikin |
E596172
|
entity |
| Predicate | hasAftereffects |
P43304
|
FINISHED |
| Object | formation of a subsidence crater |
—
|
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: formation of a subsidence crater | Statement: [Cannikin, hasAftereffects, formation of a subsidence crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAftereffects Context triple: [Cannikin, hasAftereffects, formation of a subsidence crater]
-
A.
hasAftermovie
Indicates that an event or activity is associated with a produced aftermovie documenting or summarizing it.
-
B.
aftereffect
chosen
Indicates that one event or condition occurs as a consequence or lingering result of a preceding event or condition.
-
C.
hasEffectNamedAfter
Indicates that an entity has an effect or phenomenon that is named after another entity.
-
D.
hasAfterMovie
Indicates that one movie or media work occurs or is intended to be watched immediately after another as a follow-up or subsequent viewing.
-
E.
hasFunctionAfterFilming
Indicates that an entity participates in or hosts a function or event that takes place after a filming activity has concluded.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db15866c8190ab931216b8d9c57f |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.