Triple
T21305517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS King George VI |
E525186
|
entity |
| Predicate | weaponSystemCategory |
P89527
|
FINISHED |
| Object | sea-based nuclear weapons platform |
—
|
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: sea-based nuclear weapons platform | Statement: [HMS King George VI, weaponSystemCategory, sea-based nuclear weapons platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponSystemCategory Context triple: [HMS King George VI, weaponSystemCategory, sea-based nuclear weapons platform]
-
A.
weaponSystemType
chosen
Indicates the specific category or kind of weapon system associated with an entity.
-
B.
weaponCategory
Indicates the classification or type of weapon to which an item or armament belongs.
-
C.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
D.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
E.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa3f90481909b212bdbf00c2bb0 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.