Triple
T16384442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalin’s organ |
E397884
|
entity |
| Predicate | appliedToWeaponType |
P116392
|
FINISHED |
| Object | multiple rocket launcher |
—
|
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: multiple rocket launcher | Statement: [Stalin’s organ, appliedToWeaponType, multiple rocket launcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToWeaponType Context triple: [Stalin’s organ, appliedToWeaponType, multiple rocket launcher]
-
A.
appliesToWeaponSystem
chosen
Indicates that something (such as a rule, configuration, or characteristic) is relevant or applicable to a particular weapon system.
-
B.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
relatedToWeaponType
Indicates that an entity has an association or connection with a specific type or category of weapon.
-
D.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
E.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319de83248190b5d43646fa9b6cda |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.