Triple
T20512497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atomic Bomb Hypocenter in Nagasaki |
E503598
|
entity |
| Predicate | bombingAltitude |
P6020
|
FINISHED |
| Object | approximately 500 meters above ground |
—
|
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 500 meters above ground | Statement: [Atomic Bomb Hypocenter in Nagasaki, bombingAltitude, approximately 500 meters above ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombingAltitude Context triple: [Atomic Bomb Hypocenter in Nagasaki, bombingAltitude, approximately 500 meters above ground]
-
A.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
B.
hasAltitudeOfDetonation
chosen
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
C.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
D.
bombingPlatform
Indicates that one entity serves as the platform or means from which another entity conducts or carries out a bombing.
-
E.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcd74c48190b050e25c20154c09 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.