Triple
T18582962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Tangshan earthquake |
E454162
|
entity |
| Predicate | deadlinessRanking |
P101140
|
FINISHED |
| Object | one of the deadliest earthquakes in recorded history |
—
|
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 in recorded history | Statement: [1976 Tangshan earthquake, deadlinessRanking, one of the deadliest earthquakes in recorded history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadlinessRanking Context triple: [1976 Tangshan earthquake, deadlinessRanking, one of the deadliest earthquakes in recorded history]
-
A.
deadliestIn
Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
-
B.
lethality
Indicates the degree to which something is capable of causing death or fatal harm.
-
C.
deathTollRanking
chosen
Indicates the relative position of an event or entity when ordered by the number of deaths it caused, typically from highest to lowest.
-
D.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543d10b1c8190a401df810b7290c9 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.