Triple
T31507285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard class |
E803851
|
entity |
| Predicate | strategicWeaponSystem |
P106695
|
FINISHED |
| Object | Trident II D5 |
—
|
NE NERFINISHED |
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: Trident II D5 | Statement: [Vanguard class, strategicWeaponSystem, Trident II D5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicWeaponSystem Context triple: [Vanguard class, strategicWeaponSystem, Trident II D5]
-
A.
isStrategicWeapon
chosen
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
B.
opposingWeaponSystem
Indicates that one weapon system is designed, used, or configured to counter, neutralize, or operate in direct opposition to another weapon system.
-
C.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
D.
tacticalSystem
Indicates a relationship where an entity functions as or is associated with a tactical system used for planning, coordinating, or executing tactical operations.
-
E.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 9:48 p.m.