Triple
T140569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | atomic bombing of Nagasaki |
E2840
|
entity |
| Predicate | hasImmediateDeathsEstimate |
P700
|
FINISHED |
| Object | approximately 40000 to 75000 people |
—
|
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: approximately 40000 to 75000 people | Statement: [atomic bombing of Nagasaki, hasImmediateDeathsEstimate, approximately 40000 to 75000 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmediateDeathsEstimate Context triple: [atomic bombing of Nagasaki, hasImmediateDeathsEstimate, approximately 40000 to 75000 people]
-
A.
deathTollEstimate
chosen
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
B.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
C.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
D.
mortalityRate
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
E.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257c7e79c8190b3e5a2983035a972 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.