Triple
T14164129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Centerboard I |
E351024
|
entity |
| Predicate | bombCoreMaterial |
P16405
|
FINISHED |
| Object | enriched uranium-235 |
—
|
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: enriched uranium-235 | Statement: [Operation Centerboard I, bombCoreMaterial, enriched uranium-235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombCoreMaterial Context triple: [Operation Centerboard I, bombCoreMaterial, enriched uranium-235]
-
A.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
B.
bombLoad
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
-
C.
nuclearMaterial
chosen
Indicates that the subject entity is or contains nuclear material, or is directly associated with nuclear substances used for energy, research, or weapons.
-
D.
controlRodMaterial
Indicates the material from which a control rod is made in a nuclear or control system context.
-
E.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.