Triple
T21789600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1939 Erzincan earthquake |
E537933
|
entity |
| Predicate | deadliestInCentury |
P126019
|
FINISHED |
| Object | one of the deadliest earthquakes of the 20th century |
—
|
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: one of the deadliest earthquakes of the 20th century | Statement: [1939 Erzincan earthquake, deadliestInCentury, one of the deadliest earthquakes of the 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadliestInCentury Context triple: [1939 Erzincan earthquake, deadliestInCentury, one of the deadliest earthquakes of the 20th century]
-
A.
deadliestIn
Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
-
B.
centuryOfDeath
Indicates the specific century during which an entity (typically a person) died.
-
C.
diedInCentury
Indicates that an entity’s death occurred during a specified century.
-
D.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
E.
notableDeathTollEvent
chosen
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621ed2b481909e3df17aee9cd8f7 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.