Triple
T140591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | atomic bombing of Nagasaki |
E2840
|
entity |
| Predicate | hasAltitudeOfDetonation |
P6020
|
FINISHED |
| Object | air burst above the city |
—
|
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: air burst above the city | Statement: [atomic bombing of Nagasaki, hasAltitudeOfDetonation, air burst above the city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltitudeOfDetonation Context triple: [atomic bombing of Nagasaki, hasAltitudeOfDetonation, air burst above the city]
-
A.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
hasAtmosphericPressureAtSeaLevel
Indicates that an entity possesses a specific value of atmospheric pressure measured at sea level.
-
C.
radiusOfSevereDestruction
Indicates the distance from a central point within which damage or destruction is expected to be extremely severe.
-
D.
firstNuclearTestLocation
Indicates the place where an entity conducted its first nuclear test.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.