Triple
T53779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | atomic bombing of Hiroshima |
E1059
|
entity |
| Predicate | firstUseOf |
P1588
|
FINISHED |
| Object | nuclear weapon in war |
—
|
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: nuclear weapon in war | Statement: [atomic bombing of Hiroshima, firstUseOf, nuclear weapon in war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseOf Context triple: [atomic bombing of Hiroshima, firstUseOf, nuclear weapon in war]
-
A.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
B.
firstDemonstrated
chosen
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
firstUsedInElection
Indicates that something (such as a method, technology, or rule) was used for the first time in a particular election.
-
E.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.