Triple
T34984269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-bomb |
E1008897
|
entity |
| Predicate | requiresTrigger |
P200416
|
FINISHED |
| Object | fission bomb |
—
|
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: fission bomb | Statement: [H-bomb, requiresTrigger, fission bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTrigger Context triple: [H-bomb, requiresTrigger, fission bomb]
-
A.
requiresSchedule
Indicates that an entity must have a planned schedule or timetable established before it can occur, operate, or be fulfilled.
-
B.
requiresNotificationTo
Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
-
C.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
D.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
E.
requiresCall
Indicates that one entity must initiate or receive a phone call or similar direct voice communication with another entity as a necessary condition for some action or state.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
| PDg | Predicate description generation | batch_69ff891d54248190be8742197564605a |
completed | May 9, 2026, 7:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.