Triple
T2198015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Boy |
E50421
|
entity |
| Predicate | firstUseContext |
P6318
|
FINISHED |
| Object | first nuclear weapon used in warfare |
—
|
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: first nuclear weapon used in warfare | Statement: [Little Boy, firstUseContext, first nuclear weapon used in warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseContext Context triple: [Little Boy, firstUseContext, first nuclear weapon used in warfare]
-
A.
firstBroadcastContext
Indicates the context or setting (such as channel, platform, or program) in which something was first broadcast.
-
B.
firstUseOptionRetained
Indicates that the option selected or used first in a given context is preserved and carried forward for subsequent use or reference.
-
C.
firstUsedFor
chosen
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
D.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
E.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf79f3e08190b56e9d7c0ff27237 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.