Triple
T31970196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanker |
E816290
|
entity |
| Predicate | appliesToWeaponRole |
P84541
|
FINISHED |
| Object | land-based strategic missile |
—
|
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: land-based strategic missile | Statement: [Spanker, appliesToWeaponRole, land-based strategic missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWeaponRole Context triple: [Spanker, appliesToWeaponRole, land-based strategic missile]
-
A.
appliesToWeaponSystem
Indicates that something (such as a rule, configuration, or characteristic) is relevant or applicable to a particular weapon system.
-
B.
refersToArmamentRole
chosen
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
C.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
D.
usedOnWeaponSystem
Indicates that something (such as a component, technology, or material) is employed as part of, or in conjunction with, a weapon system.
-
E.
isStartingWeaponFor
Indicates that a weapon is the initial or default weapon assigned to or used by an entity at the start of a game, scenario, or progression.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 12:10 a.m.