Triple
T25127516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 Bucharest earthquake |
E629433
|
entity |
| Predicate | casualtiesInBucharest |
P35438
|
FINISHED |
| Object | over 1400 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 1400 deaths | Statement: [1977 Bucharest earthquake, casualtiesInBucharest, over 1400 deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesInBucharest Context triple: [1977 Bucharest earthquake, casualtiesInBucharest, over 1400 deaths]
-
A.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
B.
casualtiesAssociatedWithEvent
chosen
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
C.
battleCasualty
Indicates that an entity was killed, wounded, or otherwise harmed as a direct result of a specific battle or armed conflict.
-
D.
casualtiesGothic
Indicates that an event or action resulted in casualties specifically among Gothic people or forces.
-
E.
casualtiesDescription
Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
- 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_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:28 a.m.