Triple
T999172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagasaki Atomic Bomb Museum |
E21564
|
entity |
| Predicate | dedicatedToEvent |
P1283
|
FINISHED |
| Object | atomic bombing of Nagasaki |
—
|
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: atomic bombing of Nagasaki | Statement: [Nagasaki Atomic Bomb Museum, dedicatedToEvent, atomic bombing of Nagasaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToEvent Context triple: [Nagasaki Atomic Bomb Museum, dedicatedToEvent, atomic bombing of Nagasaki]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
dedicated
chosen
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
C.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
-
D.
partOfEvent
Indicates that one entity is a component, segment, or sub-activity that belongs to or occurs within a larger event.
-
E.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e3d8b081908e536928e7d6199d |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.