Triple
T26509120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Nepal earthquake |
E669629
|
entity |
| Predicate | mainshockFollowedBy |
P159219
|
FINISHED |
| Object | numerous 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: numerous aftershocks | Statement: [2015 Nepal earthquake, mainshockFollowedBy, numerous aftershocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainshockFollowedBy Context triple: [2015 Nepal earthquake, mainshockFollowedBy, numerous aftershocks]
-
A.
mainshockDate
Indicates the date on which the primary or largest earthquake event (the mainshock) in a seismic sequence occurred.
-
B.
mainshockTimeUTC
Indicates the date and time of the primary (main) earthquake event expressed in Coordinated Universal Time (UTC).
-
C.
mainSeries
Indicates that one creative work is the primary or canonical series to which another related work (such as a spin-off, side story, or adaptation) belongs.
-
D.
يتبعها
chosen
Indicates that one entity comes after, succeeds, or is subordinate to another in order, sequence, or hierarchy.
-
E.
suppressedFollowing
Indicates that one entity’s act of following another has been intentionally hidden, blocked, or not allowed to occur.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 1:18 a.m.