Triple
T9200628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Christchurch earthquake sequence |
E220827
|
entity |
| Predicate | afters shocksCount |
P84693
|
FINISHED |
| Object | thousands of aftershocks |
—
|
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: thousands of aftershocks | Statement: [2011 Christchurch earthquake sequence, afters shocksCount, thousands of aftershocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afters shocksCount Context triple: [2011 Christchurch earthquake sequence, afters shocksCount, thousands of aftershocks]
-
A.
aftershockCount
chosen
Indicates the number of aftershocks that occur following a primary seismic event.
-
B.
aftershocks
Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
-
C.
frontShockTowers
Indicates a relationship where front shock towers are present on, attached to, or associated with a vehicle’s front suspension or chassis.
-
D.
suspensionRear
Indicates that the relationship or action involves the rear suspension component or system of an object, typically a vehicle.
-
E.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9429b448190a078e9cdfedd4918 |
completed | April 1, 2026, 8:37 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.