Triple
T37039196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redoutable-class SSBNs |
E916731
|
entity |
| Predicate | nuclearWarheadType |
P61965
|
FINISHED |
| Object | French thermonuclear warheads |
—
|
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: French thermonuclear warheads | Statement: [Redoutable-class SSBNs, nuclearWarheadType, French thermonuclear warheads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWarheadType Context triple: [Redoutable-class SSBNs, nuclearWarheadType, French thermonuclear warheads]
-
A.
nuclearExplosiveType
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
B.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
C.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
D.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
E.
warheadName
Indicates the specific name or designation assigned to a warhead associated with an entity or 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.