Triple
T25127515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 Bucharest earthquake |
E629433
|
entity |
| Predicate | casualtiesInRomania |
P84069
|
FINISHED |
| Object | over 1500 deaths |
—
|
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: over 1500 deaths | Statement: [1977 Bucharest earthquake, casualtiesInRomania, over 1500 deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesInRomania Context triple: [1977 Bucharest earthquake, casualtiesInRomania, over 1500 deaths]
-
A.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
B.
casualtiesCountry
chosen
Indicates that the specified country is the one in which the recorded casualties (deaths or injuries) occurred or to which those casualties belong.
-
C.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
primaryCasualtiesFrom
Indicates that an entity is the main source or cause of the casualties experienced by another entity.
-
E.
battleCasualty
Indicates that an entity was killed, wounded, or otherwise harmed as a direct result of a specific battle or armed conflict.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465f4fd9c81909bd0c65aee986554 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:28 a.m.