Triple
T560687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fat Man |
E13442
|
entity |
| Predicate | casualtiesCategory |
P12810
|
FINISHED |
| Object | mass civilian casualties |
—
|
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: mass civilian casualties | Statement: [Fat Man, casualtiesCategory, mass civilian casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesCategory Context triple: [Fat Man, casualtiesCategory, mass civilian casualties]
-
A.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
B.
casualtiesDescription
Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
-
C.
fatalitiesCategory
chosen
Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
-
D.
casualtiesImpact
Indicates how the number or severity of casualties affects or influences another factor, situation, or outcome.
-
E.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e2795c8190903240e79964156d |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.