Triple
T22352799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 İzmit earthquake |
E552575
|
entity |
| Predicate | aftershockSequence |
P3828
|
FINISHED |
| Object | strong aftershocks for weeks |
—
|
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: strong aftershocks for weeks | Statement: [1999 İzmit earthquake, aftershockSequence, strong aftershocks for weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftershockSequence Context triple: [1999 İzmit earthquake, aftershockSequence, strong aftershocks for weeks]
-
A.
aftershockCount
Indicates the number of aftershocks that occur following a primary seismic event.
-
B.
earthquakeSequence
Indicates a relationship where multiple earthquakes are linked as part of the same temporal or causal sequence of seismic events.
-
C.
aftershocks
chosen
Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
-
D.
hasTsunamiSequence
Indicates that an event or location is associated with a sequence of tsunami occurrences or related tsunami phenomena.
-
E.
foreshocks
Indicates that an earthquake occurs as a smaller, preceding seismic event that happens before a larger mainshock in the same region.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1579cbbe88190bf2f27d34fc8f30e |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.